Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Outdated ca-cert path for Jolokia trait #2827

Closed
tadayosi opened this issue Dec 9, 2021 · 1 comment
Closed

Outdated ca-cert path for Jolokia trait #2827

tadayosi opened this issue Dec 9, 2021 · 1 comment
Assignees

Comments

@tadayosi
Copy link
Member

tadayosi commented Dec 9, 2021

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

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

@tadayosi tadayosi self-assigned this Dec 9, 2021
tadayosi added a commit to tadayosi/camel-k that referenced this issue Dec 9, 2021
tadayosi added a commit to tadayosi/camel-k that referenced this issue Dec 9, 2021
@tadayosi
Copy link
Member Author

tadayosi commented Dec 9, 2021

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.

Closing.

@tadayosi tadayosi closed this as completed Dec 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant