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

java client is not taking the updated ca.crt/token and error out #3809

Open
suryag10 opened this issue Nov 29, 2024 · 3 comments
Open

java client is not taking the updated ca.crt/token and error out #3809

suryag10 opened this issue Nov 29, 2024 · 3 comments

Comments

@suryag10
Copy link

Describe the bug
updated ca.crt/token are not considered by the java k8s client and errors out
java.util.concurrent.ExecutionException: io.kubernetes.client.openapi.ApiException: javax.net.ssl.SSLHandshakeException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed

Client Version
17.0.2

Kubernetes Version
1.21.12

Java Version
openjdk 17.0.12 2024-07-16 LTS

To Reproduce
update the k8s ca.crt and token with the new certificates.

Expected behavior
Java client should consider the latest ca.crt and token and K8S API access should succeed

Server (please complete the following information):

  • OS: Linux
  • Environment : Container
  • Cloud : Vanilla K8S
@suryag10
Copy link
Author

Any Help here?

@brendandburns
Copy link
Contributor

Yeah, the current auth code doesn't reload certificates if the files change. It would be a fairly significant effort to do so, but if you wanted to take it on, we'd be happy to review the design/PRs.

@suryag10
Copy link
Author

suryag10 commented Dec 3, 2024

Thanks @brendandburns , Will check if i can submit the PR for the same.

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

No branches or pull requests

2 participants