-
Notifications
You must be signed in to change notification settings - Fork 988
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
Support KUBERNETES_EXEC_INFO
env var for exec
provider configuration
#1495
Comments
@z0rc I assume that the provider would work with |
@stevehipwell I didn't think through the overrides and/or priority order of configuration at this case. Hopefully this can be prioritized with kubectl 1.24 deprecating v1alpha1 client auth version. |
Reading more into this issue, my initial assumption about setting env var was wrong.
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
For a long time
aws eks get-token
returnedapiVersion: client.authentication.k8s.io/v1alpha1
, there was attempt to switch it to v1beta1, but was hastly reverted, see aws/aws-cli#6289 and aws/aws-cli#6309.Now aws-cli is going to approach this in planned manner and make it configurable, see aws/aws-cli#6476. It's planned to honor env var
KUBERNETES_EXEC_INFO
, which is documented here https://kubernetes.io/docs/reference/access-authn-authz/_print/#input-and-output-formatsAs provider's
exec
configuration requiresapi_version
attribute, it will make hard for module authors to support multiple aws-cli versions, once it makes a switch.Please make this provider support
KUBERNETES_EXEC_INFO
as source ofapi_version
value, and potentially other attributes too.Potential Terraform Configuration
Following snippet should work when
KUBERNETES_EXEC_INFO
is set and valid.References
cloudposse/terraform-aws-eks-cluster#131 here is problem that module authors has to deal with.
Community Note
The text was updated successfully, but these errors were encountered: