Skip to content
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

presented server name type wasn't supported on GKE #388

Closed
tamasfe opened this issue Sep 11, 2022 · 2 comments
Closed

presented server name type wasn't supported on GKE #388

tamasfe opened this issue Sep 11, 2022 · 2 comments
Assignees
Labels
bug Something isn't working user

Comments

@tamasfe
Copy link
Contributor

tamasfe commented Sep 11, 2022

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

  1. gcloud container clusters get-credentials foo: load cluster credentials into .kube/config
  2. k describe node: kubectl connects successfully
  3. try to mirrord exec anything in the cluster

Backtrace

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

@tamasfe tamasfe added the bug Something isn't working label Sep 11, 2022
@aviramha
Copy link
Member

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.

@eyalb181
Copy link
Member

Hey @tamasfe, this should be fixed in the latest version. Please let us know if it reproduces.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working user
Projects
None yet
Development

No branches or pull requests

4 participants