instance-selector is now patched to work w/ EKS AMI V20220123 #4682
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
ec2-instance-selector was unnecessarily validating that the version of the EKS AMI (https://github.com/awslabs/amazon-eks-ami/releases/tag/v20220123) was prepended with a lowercase
v
. But the latest release of the AMI had an uppercaseV
(has since been fixed). A patch was put into place in eksctl (#4681). The EC2 Instance Selector has since been patched (aws/amazon-ec2-instance-selector#112) and so the eksctl patch can be reverted and point to the latest commit of the official instance-selector repo.Checklist
README.md
, or theuserdocs
directory)area/nodegroup
) and kind (e.g.kind/improvement
)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯