-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Highlight the need to tag subnets #1904
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
Conversation
Welcome @isqrd! |
Hi @isqrd. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
docs/guide/service/nlb_ip_mode.md
Outdated
@@ -33,5 +33,22 @@ to enable proxy protocol v2, apply the following annotation to your service: | |||
service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: "*" | |||
``` | |||
|
|||
## Subnet tagging requirements | |||
You must tag the subnets you wish to attach your ELB to with the following tags. |
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.
Subnets tags are useful only for auto-discovery.
docs/guide/service/nlb_ip_mode.md
Outdated
## Subnet tagging requirements | ||
You must tag the subnets you wish to attach your ELB to with the following tags. | ||
- For any subnet used by node group. | ||
- **Key:** *kubernetes.io/cluster/$CLUSTER_NAME* |
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.
The cluster tag is optional. In case of ties (for example there are multiple subnets in the same AZ), auto-discovery will prefer the one with the cluster tag. This has been the behavior since EKS 1.19 for in-tree and v2.1.2 release of the lb controller (ref https://docs.aws.amazon.com/eks/latest/userguide/load-balancing.html)
Lets reference the file deploy/subnet_discovery.md instead. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: isqrd, kishorj 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 |
While this info is part of the AWS eks userguid documentation, I think it is worth including the need to tag subnets with kubernetes.io/role/ tag here as well.