-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Relax cluster tag requirement on subnets during auto-discovery #1773
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
Hi @kishorj. 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. |
Codecov Report
@@ Coverage Diff @@
## main #1773 +/- ##
==========================================
+ Coverage 46.76% 46.91% +0.15%
==========================================
Files 110 110
Lines 5988 6007 +19
==========================================
+ Hits 2800 2818 +18
- Misses 2925 2926 +1
Partials 263 263
Continue to review full report at Codecov.
|
/label tide/merge-method-squash |
/ok-to-test |
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
/test pull-aws-load-balancer-controller-e2e-test |
/test pull-aws-load-balancer-controller-e2e-test |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: kishorj, M00nF1sh 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 |
Release 2.1.2 included changes that relaxed requirements on subnet [tagging](kubernetes-sigs#1773) with the cluster name.
* docs: update Subnet discovery with optional tag Release 2.1.2 included changes that relaxed requirements on subnet [tagging](#1773) with the cluster name. * docs: update based of PR feedback
* These tags were previously required by aws-load-balancer-controller/alb-ingress-controller * We no longer ship a ingress controller with the module since #225 * aws-load-balancer-controller doesn't need those tags anyway since v2.1.2 - kubernetes-sigs/aws-load-balancer-controller#1773
* These tags were previously required by aws-load-balancer-controller/alb-ingress-controller * We no longer ship a ingress controller with the module since #225 * aws-load-balancer-controller doesn't need those tags anyway since v2.1.2 - kubernetes-sigs/aws-load-balancer-controller#1773
…netes-sigs#1773) * relax cluster tag requirement on subnets * handle subnets with multiple cluster tags
* docs: update Subnet discovery with optional tag Release 2.1.2 included changes that relaxed requirements on subnet [tagging](kubernetes-sigs#1773) with the cluster name. * docs: update based of PR feedback
Relax the kubernetes cluster tag requirement on subnets during auto-discovery. The prior behavior was to discover only those subnets with the tag
kubernetes.io/cluster/<clustername>
and values{owned, shared}
. If there are subnets with the cluster tag, those still get choosen. In case there are multiple subnets per AZ, auto-discovery will break the tie in the following orderIf the subnet has tag for a different cluster, auto-discovery will ignore such subnets.
Tests done