-
Notifications
You must be signed in to change notification settings - Fork 218
SunCertPathBuilderException: unable to find valid certification path to requested target when connecting to k3d #996
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
Comments
Here's the complete stack trace:
|
The issue is that the fabric8 client cannot process certificates using elliptical curve encryption by default, which <dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcpkix-jdk15on</artifactId>
</dependency> |
Unfortunately, that didn't help. Still getting the same error. |
Here's the full commandline:
|
Sorry but I'm not too familiar with gradle but it seems you might need to tell IDEA to refresh its dependencies because the BouncyCastle dependency doesn't appear to be put in class path argument in the command line you pasted. |
Duh, you are correct. Refreshing the caches did the trick, thank you! This sounds like it might be an FAQ... (the missing dependency, not my inability to use IntelliJ correctly.) |
Yes, I was thinking about the FAQ, indeed. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
@metacosm can we close this issue now? |
I don't recall if we ever created a FAQ entry for this… If we did, we can close it. If we didn't, we need to create one then close it ;) |
Bug Report
What did you do?
I have an operator running fine in Docker Desktop/Kubernetes. I need to make it work in Docker Desktop/k3d. Starting the operator from IntelliJ fails on startup.
What did you expect to see?
The operator should start and connect to the cluster.
What did you see instead? Under which circumstances?
Environment
Kubernetes cluster type:
Docker Desktop with k3d
implementation 'io.javaoperatorsdk:operator-framework-spring-boot-starter:2.0.1'
$ java -version
$ kubectl version
Possible Solution
I thought that setting the system property
-Dkubernetes.trust.certificates=true
(for the fabric8 client) should disable the certificate verification, but that had no effect.I've also set the Spring Boot property
javaoperatorsdk.client.trustSelfSignedCertificates=true
and verified with the debugger that it is set, but there is no change.The text was updated successfully, but these errors were encountered: