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
When using a kubeconfig which defines a tls-server-name field different from the server field, the client fails to validate the cluster certificate.
As a workaround, setting insecure-skip-tls-verify: true and removing certificate-authority-data from the kubeconfig file works.
Client Version
20
Kubernetes Version
1.28.6
Java Version
17
To Reproduce
Get a kubeconfig with a tls-server-name field different from the server field. This is the case with the kubeconfig files generated by Teleport. Run the KubeConfigFileClientExample.java:
cd examples/examples-release-20
mvn -X clean install exec:java -Dexec.mainClass="io.kubernetes.client.examples.KubeConfigFileClientExample"
Expected behavior
The client respects the tls-server-name field and uses this hostname to verify the TLS certificate.
Yeah, that's not currently supported in our TLS. We'd be happy to take a PR to add support.
I’m not a Java developer, I reported this issue because some applications from my company use the Java client and some of our customers use Teleport so the said apps don’t work for them.
Our Java developer don’t have any bandwidth to take this matter into his hands, so I hope someone could work on this 🙏
Describe the bug
When using a kubeconfig which defines a
tls-server-name
field different from theserver
field, the client fails to validate the cluster certificate.As a workaround, setting
insecure-skip-tls-verify: true
and removingcertificate-authority-data
from the kubeconfig file works.Client Version
20
Kubernetes Version
1.28.6
Java Version
17
To Reproduce
Get a kubeconfig with a
tls-server-name
field different from theserver
field. This is the case with the kubeconfig files generated by Teleport. Run theKubeConfigFileClientExample.java
:Expected behavior
The client respects the
tls-server-name
field and uses this hostname to verify the TLS certificate.KubeConfig
Server (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: