Background:
Connecting to Jolokia enabled pods in kubernetes have used the Kubernetes API proxy capabilty /api/v1/namespaces/ns/pods/http:pod:port/proxy/jolokia/
Ongoing research:
While working on a PR for JMC I have been made aware that the support for proxy directly to pods is a lot less simple in later versions of Kubernetes. I fear that this strategy is no longer feasible. Will post findings.
Workaround:
Use port forward to the pod in question and connect over the Jolokia protocol instead.
Background:
Connecting to Jolokia enabled pods in kubernetes have used the Kubernetes API proxy capabilty /api/v1/namespaces/ns/pods/http:pod:port/proxy/jolokia/
Ongoing research:
While working on a PR for JMC I have been made aware that the support for proxy directly to pods is a lot less simple in later versions of Kubernetes. I fear that this strategy is no longer feasible. Will post findings.
Workaround:
Use port forward to the pod in question and connect over the Jolokia protocol instead.