feat: Upgrade EKS Module from Version 17.23 to 20 #220
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
amanpruthi
changed the title
amanpruthi
changed the title
amanpruthi
changed the title
|
@zacharyblasczyk - Do you think this is needed? If yes, would it possible to review by next week? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Upgrade EKS Module from Version 17.23 to 20
./eks_module_upgrade.sh --pre. This script will check for the Terraform binary, ensure the presence of the terraform.tfstate file, and execute the necessary terraform state mv and terraform state rm commands../eks_module_upgrade.sh --post <cluster_name> <aws_region>. This script will check for the AWS CLI and update the kubeconfig for the specified <cluster_name>. If the AWS_DEFAULT_REGION environment variable is set, the <aws_region> parameter is optional. The script will then drain and delete the old node group from the EKS cluster and migrate the workload to the new node group.