fix: Use variable to enable EKS cluster creation with CONFIG_MAP authentication mode #3270
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Using
enable_cluster_creator_admin_permissionsvariable forbootstrap_cluster_creator_admin_permissionsin place of hard codedfalsevalue to support EKS cluster creation when authentication mode isCONFIG_MAPonly. I think alternatively we can use API_AND_CONFIG_MAP, but this will take time for us to migrate our clusters and customers clusters.Motivation and Context
It allows a user to create an EKS cluster when authentication mode is
CONFIG_MAPonly by usingbootstrap_cluster_creator_admin_permissions=true.Without this value, the user will be facing the below error.
It fixes the following open issue.
#3247
Breaking Changes
The default value for
bootstrap_cluster_creator_admin_permissionsvariable is stillfalse. So it doesn't break anything.How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request