A ClusterIP exposes the following: spec.clusterIp:spec.ports[*].port You can only access this service while inside the cluster. It is accessible from its spec.clusterIp port. If a spec.ports[*].targetPort is set it will route from the port to the targetPort. The CLUSTER-IP you get when calling kubectl get services is the IP assigned to this service within the … Read more
You can do a DNS query from any pod and you would get the FQDN. # nslookup api-server Server: 10.96.0.10 Address: 10.96.0.10#53 Name: api-server.default.svc.cluster.local Address: 10.104.225.18 root@api-server-6ff8c8b9c-6pgkb:/# cluster-domain.example is just a example in the documentation. cluster.local is the default cluster domain assigned. So the FQDN of any service by default would be <service-name>.<namespace>.svc.cluster.local. You don’t … Read more
Usually, you refer to a target port by its number. But you can give a specific name to each pod`s port and refer to this name in your service specification. This will make your service clearer. Here a small example: apiVersion: v1 kind: Pod metadata: name: named-port-pod labels: app: named-port-pod spec: containers: – name: echoserver … Read more
Another option is to forward JMX port from K8 pod to your local PC with kubectl port-forward. I do it like this: 1). Add following JVM options to your app: -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.port=1099 -Dcom.sun.management.jmxremote.rmi.port=1099 -Djava.rmi.server.hostname=127.0.0.1 The critical part here is that: The same port should be used as ‘jmxremote.port’ and ‘jmxremote.rmi.port’. This is … Read more
URL of service is in the below format: <service-name>.<namespace>.svc.cluster.local:<service-port> In your case it is: helloworldsvc.test.svc.cluster.local:9111
[*] A ClusterIP exposes the following: spec.clusterIp:spec.ports[*].port You can only access this service while inside the cluster. It is accessible from its spec.clusterIp port. If a spec.ports[*].targetPort is set it will route from the port to the targetPort. The CLUSTER-IP you get when calling kubectl get services is the IP assigned to this service within … Read more