-
Notifications
You must be signed in to change notification settings - Fork 78
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
Support for the ENI_CONFIG_LABEL_DEF environment variable #411
Conversation
closing this, will reopen after it passes internal review. |
The build error in travis ci does not seem related to my change, seems like an env var is not getting set, from what I can tell:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution! 🎉
Overall LGTM just a comment
No worries, I'll have to shepherd this PR through since the secrets are not available for public use. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🎉
Thanks for the changes!
Will pull this in for testing and aim to merge it if all goes green.
Merged this PR in via #412 |
Proposed changes
When an EKS cluster worker node group is spread across multiple availability zones,
and we want to use custom CNI networking, EKS allows you to specify the
ENI_CONFIG_LABEL_DEF environment variable value for worker nodes
This is used to tell Kubernetes to automatically apply the ENIConfig for each Availability Zone
Ref: https://docs.aws.amazon.com/eks/latest/userguide/cni-custom-network.html (step 6(c)).
This PR exposes the env variable in the CNI module in pulumi-eks.
Related issues (optional)
Addresses issue #410