Unable to connect to K8s cluster due to mismatch in client authentication api version #37
Comments
|
Hello @jimvmathews, thanks for reporting! What's your cluster version? |
|
Hey @jimvmathews, you can give it another shot now. I've updated the awscli and kubectl versions - could you let me know if it feels better now? Thanks! |
|
Good morning @koslib, I had the same problem now, do I need to change something first? |
|
Hey @brunoflegler what's your cluster version? The only think I can imagine is kubectl being on a version not compatible with your cluster version, so let's start from there and we can gradually drill down to it. |
|
Hey @koslib, my cluster is at version 1.21. |
|
@brunoflegler can you try with action version |
|
Hi @koslib , I did the test yesterday and yes it works fixing the mentioned version. |
See koslib/helm-eks-action#37 (comment) for more * We're using the master version of the helm github action * It recently had an update that featured a kubectl version update * This has had the knock on effect of causing our helm deploys to fail with ``` invalid apiVersion "client.authentication.k8s.io/v1alpha1" ```
See koslib/helm-eks-action#37 (comment) for more * We're using the master version of the helm github action * It recently had an update that featured a kubectl version update * This has had the knock on effect of causing our helm deploys to fail with ``` invalid apiVersion "client.authentication.k8s.io/v1alpha1" ```
|
Thanks @brunoflegler for getting back to me on that! To be honest I don't see any other option other than sticking with version How do you recommend this is handled? Because the action needs to be updated with fresh dependency versions, however I understand that some users might need to use older versions still. Would it make sense potentially to have branches based on k8s versions as well as relevant tagging? Any other ideas? At least I'm glad this is no longer an ongoing issue for you, even with this workaround stuff is working on your end:) |
|
Seems to be duplicate of #41 - closing this one and continuing discussion there |
Unable to connect to K8s cluster due to mismatch in client authentication api version
Error:
Error: Kubernetes cluster unreachable: Get "https://5a51c73d67a28d21c8038197f2d67054.sk1.us-west-1.eks.amazonaws.com/version": getting credentials: exec plugin is configured to use API version client.authentication.k8s.io/v1beta1, plugin returned version client.authentication.k8s.io/v1alpha1
The text was updated successfully, but these errors were encountered: