You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default CA cert path /var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt for Jolokia trait seems to be outdated. When I run an integration as follows, I get No such CA cert error and cannot enable Jolokia endpoint:
$ kamel run examples/languages/Sample.java -t jolokia.enabled=true -t jolokia.protocol=https --dev
...
Could not start Jolokia agent: java.lang.IllegalStateException: Cannot open keystore for https communication: java.io.FileNotFoundException: No such CA cert /var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt
Hmm, it looks like it's my mistake. For OpenShift there has been /var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt and it's the correct path.
The default CA cert path
/var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt
for Jolokia trait seems to be outdated. When I run an integration as follows, I getNo such CA cert
error and cannot enable Jolokia endpoint:The correct path would be
/var/run/secrets/kubernetes.io/serviceaccount/ca.crt
:https://kubernetes.io/docs/tasks/access-application-cluster/access-cluster/#accessing-the-api-from-a-pod
The text was updated successfully, but these errors were encountered: