-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Add support for custom env vars in amazon-vpc-cni #8276
Add support for custom env vars in amazon-vpc-cni #8276
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rifelpet The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test pull-kops-verify-govet |
/hold cancel |
38d2f91
to
3ae17a4
Compare
/area api |
3ae17a4
to
d7b8e98
Compare
/test pull-kops-verify |
1 similar comment
/test pull-kops-verify |
/hold for reimplementing with #8455 |
d7b8e98
to
3d5c185
Compare
3d5c185
to
c4b6e0a
Compare
/hold cancel |
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.
Left some editorial suggestions. I'm 👍 on the substance
upup/pkg/fi/cloudup/tests/bootstrapchannelbuilder/amazonvpc/cluster.yaml
Show resolved
Hide resolved
c4b6e0a
to
e506f1b
Compare
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
/retest |
There are a handful of env vars that users often want to set when using the AWS VPC CNI (
amazonvpc
):https://github.com/aws/amazon-vpc-cni-k8s/tree/master#cni-configuration-variables
This opens them up through the cluster spec so they can be set more easily.
I was up in the air with the field name,After discussion during office hours I went withenv
like in a pod spec's container,envVar
,variables
but settled withenvironment
which is already used in exec hooks. I'm open to using a different name though.env
to match the pod spec's container field./hold since this relies on much of the test work of #8274, so waiting until that is merged
closes #7821