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

Feature: ENIConfig set by custom annotation or label names #280

Merged
merged 7 commits into from
Jan 11, 2019

Conversation

etopeter
Copy link
Contributor

@etopeter etopeter commented Jan 3, 2019

This feature enables user to set custom annotation or label key to define ENIConfig name. One use case if you have nodes in different failure domains. By default AWS deployments set node label failure-domain.beta.kubernetes.io/zone and its value is availability zone name. We can use availability zone name as ENIConfig to map to proper subnets.
Added 2 new environmental variables:
ENI_CONFIG_ANNOTATION_DEF
ENI_CONFIG_LABEL_DEF

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Copy link

@dng-dev dng-dev left a comment

Choose a reason for hiding this comment

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

Can u provide a more Detailed example. I would prefer a prefix somehow. As example eniConfig-us-east-1a or eniConfig-us-east-1b

pkg/eniconfig/eniconfig.go Show resolved Hide resolved
@mogren
Copy link
Contributor

mogren commented Jan 11, 2019

Thanks, a lot easier to follow, and thanks @nak3 for the suggestion. 🙂

@mattlandis
Copy link
Contributor

Thanks for the contribution.

/lgtm

@mogren mogren merged commit 33e9705 into aws:master Jan 11, 2019
@adammw
Copy link
Contributor

adammw commented Jan 22, 2019

@mattlandis @mogren any chance we can get a release that includes this patch? Finding it difficult to start a node that comes up with the annotation set, compared to a label which is supported via kubelet's --node-labels flag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants