Add flag to control CNI policy attachment #14
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.
Some users prefer to assign the AmazonEKS_CNI_Policy on the aws-node DaemonSet level using IRSA, rather than assigning those permissions to the worker node IAM Role. More details about this approach can be found in the AWS doc: https://docs.aws.amazon.com/eks/latest/userguide/cni-iam-role.html
Therefore to allow users to have such possibility, I have added a flag attach_worker_cni_policy, that controls the assignment of this policy. Since the policies attachment is done via a for_each loop, I have moved the policies list to locals and added a conditional to add/remove the policy based on the flag value.
Below are some basic test results when using this new setup:
I have also adjusted the Readme example module name to match the actual module name we use in all of our code and examples.