feat: Update VPC CNI policy to 3/4/24 #476
Merged
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.
Update VPC CNI policy to version released on 3/4/24. https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonEKS_CNI_Policy.html
Description
The VPC CNI policy is missing
ec2:DescribeSubnets
from the updated policy.Motivation and Context
The AWS managed VPC CNI 1.18.0 uses ec2:DescribeSubnets.
Breaking Changes
Updates VPC CNI policy.
Open issue: #474
How Has This Been Tested?
ec2:DescribeSubnets
being added.