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
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
The text was updated successfully, but these errors were encountered:
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.
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):
The text was updated successfully, but these errors were encountered: