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
kube_client::client::builder: failed with error error trying to connect: presented server name type wasn't supported is reported when connecting to a GKE cluster.
--accept-invalid-certificates as suggested is a good workaround but the certificate is definitely valid.
Thanks for reporting it - as you suggested, it's because of rustls We had problems linking to OpenSSL as the running binary might have another version required leading to crashes so we have to use rustls.
It seems that the rustls issue is a bit complicated (requires changes on dependencies that are still pending). I'll try to see if we can push something there or help somehow.
Bug Description
kube_client::client::builder: failed with error error trying to connect: presented server name type wasn't supported
is reported when connecting to a GKE cluster.--accept-invalid-certificates
as suggested is a good workaround but the certificate is definitely valid.If you are using rustls, I suspect it's rustls/rustls#184.
Steps to Reproduce
gcloud container clusters get-credentials foo
: load cluster credentials into.kube/config
k describe node
: kubectl connects successfullymirrord exec
anything in the clusterBacktrace
No response
Relevant Logs
No response
Your operating system and version
Linux 5.19.7-arch1-1
Local process
/bin/bash
Local process version
No response
Additional Info
No response
The text was updated successfully, but these errors were encountered: