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

Ability to configure apiVersion in kubeconfig exec in cluster.ts #599

Closed
TheMasterR opened this issue Jul 29, 2021 · 3 comments
Closed

Ability to configure apiVersion in kubeconfig exec in cluster.ts #599

TheMasterR opened this issue Jul 29, 2021 · 3 comments
Labels
kind/enhancement Improvements or new features resolution/by-design This issue won't be fixed because the functionality is working as designed

Comments

@TheMasterR
Copy link

It would be useful to be able to configure the apiVersion in kubeconfig for AWS credentials, as amazon changes the version from time to time.

Having mismatch apiVersion will result in an error,
EG:

kubernetes:apps/v1:Deployment XXX **creating failed** [diff: ~spec]; error: configured Kubernetes cluster is unreachable: unable to load schema information from the API server: Get "https://XXX.eu-central-1.eks.amazonaws.com/openapi/v2?timeout=32s": getting credentials: exec plugin is configured to use API version client.authentication.k8s.io/v1alpha1, plugin returned version client.authentication.k8s.io/v1beta1

Affected feature

EKS Cluster -> kubeconfig -> AWS credentials -> apiVersion

@TheMasterR TheMasterR added the kind/enhancement Improvements or new features label Jul 29, 2021
@bcmyers
Copy link

bcmyers commented Jul 31, 2021

FWIW, I'm also hitting this problem; so interested in being able to configure API version.

@lukehoban
Copy link
Contributor

This is interesting. It seems like the aws-cli change in aws/aws-cli@b82ba41 is a breaking change in a patch release. The aws tool no longer will work with any existing kubeconfig if I understand correctly. And if the kubeconfig is updated, it will not work with any earlier kubeconfig.

Ah - indeed - see aws/aws-cli#6308. It looks like another patch release was published to revert the change linked here - which should allow this to continue working.

I see they are looking at adding a flag you can pass to opt in to a version - which we may be able to use when they revisit how to correctly re-introduce this feature.

For now though, I believe we do not want to make any change in pulumi-eks here.

@lukehoban lukehoban added the resolution/by-design This issue won't be fixed because the functionality is working as designed label Jul 31, 2021
@lukehoban
Copy link
Contributor

Closing this out as currently by-design. If there's a scenario for manually controlling this outside of dealing with this breaking chance, definitely interested in the details. I believe in general it is going to be better for this package to ensure it always generates a kubeconfig that will work correctly - which might not be just about this version number.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features resolution/by-design This issue won't be fixed because the functionality is working as designed
Projects
None yet
Development

No branches or pull requests

3 participants