As of June 2020, SDM SOAP Web Services are exposed as a service only on sdmapp-0 pod.
kubectl -n casm-docker describe service sdmapp-ws gives something like:
Name: sdmapp-ws
Namespace: casm-docker
Labels: app=sdmapp-ws
Annotations: kubectl.kubernetes.io/last-applied-configuration:
{"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"labels":{"app":"sdmapp-ws"},"name":"sdmapp-ws","namespace":"casm-docker"...
Selector: app=casm,component=sdmapp,product=SDM
Type: ClusterIP
IP: X.X.X.X
Port: web-services 8080/TCP
TargetPort: 8080/TCP
Endpoints: Y.Y.Y.Y:8080
Session Affinity: None
Events: <none>
Note: Y.Y.Y.Y above would show sdmapp-0's IP address.
This might have been an oversight, steps below helps you remove the restriction
Release : 17.3
Component : SERVICE DESK MANAGER
Modify service-core.yaml for SDM container in "50 - sdm" folder to look like below.
50 - sdm\service-core.yaml
apiVersion: v1
kind: Service
metadata:
labels:
app: sdmapp-ws
name: sdmapp-ws
spec:
ports:
- name: web-services
port: 8080
protocol: TCP
targetPort: 8080
selector:
app: casm
component: sdmapp
product: SDM
options.deploy_web_services: "1"
sessionAffinity: None
type: ClusterIP
note: we removed the line statefulset.kubernetes.io/pod-name: sdmapp-0 and removed the comment in front of # options.deploy_web_services: "1"
Re-run apply.sh
Delete the pods to regenerate them again