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
Whenever using auto configuration with "EC" algo the underlying http client fails with exception: JcaPEMKeyConverter is provided by BouncyCastle, an optional dependency. To use support for EC Keys you must explicitly add this dependency to classpath.
However, this exception is buried in HttpClientUtils.java:214:
} catch (Exception e) { KubernetesClientException.launderThrowable(e); }
This causes the users of this library to look for the source of the problem in other places.
Fabric8 Kubernetes Client version
other (please specify in additional context)
Steps to reproduce
on kubernetes-client version 5.12.1
try to configure to a local k3s using auto config - it will be using EC algo
the result is that the client is burying the root cause mentioned before and it will issue a confusing exception like this: Caused by: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target which is very confusing, since this is not the cause of the problem
Expected behavior
The main cause of the failure shown in logs should be JcaPEMKeyConverter is provided by BouncyCastle, an optional dependency. To use support for EC Keys you must explicitly add this dependency to classpath. and not Caused by: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.
This can be done by not burying the initial exception.
Describe the bug
Whenever using auto configuration with "EC" algo the underlying http client fails with exception:
JcaPEMKeyConverter is provided by BouncyCastle, an optional dependency. To use support for EC Keys you must explicitly add this dependency to classpath.
However, this exception is buried in HttpClientUtils.java:214:
} catch (Exception e) { KubernetesClientException.launderThrowable(e); }
This causes the users of this library to look for the source of the problem in other places.
Fabric8 Kubernetes Client version
other (please specify in additional context)
Steps to reproduce
Expected behavior
The main cause of the failure shown in logs should be JcaPEMKeyConverter is provided by BouncyCastle, an optional dependency. To use support for EC Keys you must explicitly add this dependency to classpath. and not Caused by: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.
This can be done by not burying the initial exception.
Runtime
other (please specify in additional context)
Kubernetes API Server version
1.20.12
Environment
Linux
Fabric8 Kubernetes Client Logs
No response
Additional context
fabric8 kubernetes-client version: 1.15.2
kubernetes cluster: k3s
The text was updated successfully, but these errors were encountered: