...
We could verify the service using its CLUSTER-IP on Kubernetes master node. Note the system-generated values for the NodePorts of the two services (in this case 31156 and 30458).
Code Block | ||||
---|---|---|---|---|
| ||||
$ kubectl get svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE coffee-svc NodePort 10.110.66.194 <none> 80:31156/TCP 3d1h tea-svc NodePort 10.96.32.111 <none> 80:30458/TCP 3d1h # Verify that the service is working $ curl 10.110.66.194 Server address: 172.16.231.221:8080 Server name: coffee-6f4b79b975-v7cv2 Date: 30/Oct/2020:16:33:20 +0000 URI: / Request ID: 8d870888961431bf04dd2305d614004f |
...