If your IBM®
Streams applications run within the Kubernetes cluster, you will get the best performance if you use the Kubernetes internal host and port to form the URL to access the Streams service.
Procedure
To find the internal host and port for the Streams service, you must find the Kubernetes object name, namespace, and internal port.
-
View a list of Kubernetes services that were created by using the following command:
kubectl get svc -n <namespace>
For example, for the
Kubernetes services in a namespace called
mynamespace, where the
Streams instance is called
myinstance, the build service is called
mybuild, and the security service is called
mysecurity, you will
see the following
output:
$ kubectl get svc -n mynamespace
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
mybuild-build NodePort 192.0.2.0 <none> 8445:30720/TCP 21d
mysecurity-sso NodePort 192.0.2.1 192.0.2.15,192.0.2.16 8446:31682/TCP 21d
myinstance-console ClusterIP 192.0.2.2 <none> 9000/TCP 21d
myinstance-jmx NodePort 192.0.2.3 192.0.2.17 9975:30555/TCP,9976:31076/TCP 21d
myinstance-management ClusterIP 192.0.2.4 <none> 9000/TCP 21d
myinstance-repository ClusterIP 192.0.2.5 <none> 9000/TCP,9001/TCP 21d
myinstance-security ClusterIP 192.0.2.6 <none> 9000/TCP 21d
myinstance-sws NodePort 192.0.2.7 192.0.2.18 8443:31794/TCP 21d
-
Use the output and the following table to determine the host and port for the Kubernetes service for the Streams service that you want to access.
Table 1.
| Service |
Host |
Port |
| Streams console and Streams instance REST APIs |
<instance-name>-sws |
8443 |
| Streams build service |
<build-service-name>-build |
8445 |
| Streams security service |
<security-service-name>-sso |
8446 |
What to do next
Use the host and port in the
host:port fields of the URL for the Streams Console and the REST and JMX APIs. For more information about forming the URL to access the
Streams or the REST and JMX APIs, see Monitoring and managing IBM Streams with REST and JMX APIs.