Skip to content
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

fix: Fixed example where VPC CNI permissions should apply to the aws-node account #225

Merged

Conversation

jbronn
Copy link
Contributor

@jbronn jbronn commented Apr 15, 2022

Description

The AWS documentation uses a service account name aws-node instead of aws-vpc-cni, the Helm chart name.

Motivation and Context

Don't want someone to be misled by current documentation.

Breaking Changes

None

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects

I've successfully used aws-node in my projects and was forced to double-check the AWS documentation after seeing the example here.

@jbronn jbronn changed the title VPC CNI permissions should apply to the aws-node account. fix: VPC CNI permissions should apply to the aws-node account. Apr 15, 2022
Copy link
Member

@bryantbiggs bryantbiggs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good point, thanks for the PR - @antonbabenko 👍🏽

@antonbabenko antonbabenko changed the title fix: VPC CNI permissions should apply to the aws-node account. fix: Fixed example where VPC CNI permissions should apply to the aws-node account Apr 15, 2022
@antonbabenko antonbabenko merged commit 1fb1cfc into terraform-aws-modules:master Apr 15, 2022
antonbabenko pushed a commit that referenced this pull request Apr 15, 2022
### [4.20.1](v4.20.0...v4.20.1) (2022-04-15)

### Bug Fixes

* Fixed example where VPC CNI permissions should apply to the `aws-node` account ([#225](#225)) ([1fb1cfc](1fb1cfc))
@antonbabenko
Copy link
Member

This PR is included in version 4.20.1 🎉

@github-actions
Copy link

github-actions bot commented Nov 8, 2022

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants