add example of managing aws-auth configmap #2
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.
Summary:
This PR introduces a new example of managing AWS-auth configmap in the EKS cluster by creating a new node role, updating the node group and cluster configurations, and adding a new utility function.
Key points:
NewNodeRole
innoderole.go
to create a new node role.main.go
to use the new node role in the EKS cluster.cluster.go
to manage the AWS-auth configmap and to use the new node role.nodegroup.go
to use the new node role.ArnToRoleMapping
inutils.go
.README.md
.Generated with ❤️ by ellipsis.dev