-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
GCE: Use existing subnetwork of ILB forwarding rule #57861
Conversation
/assign bowei |
4b0b4af
to
64c2067
Compare
Test cases passed. PTAL @rramkumar1 @bowei |
LGTM |
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
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bowei, nicksardo Associated issue: #57860 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/test pull-kubernetes-e2e-gce |
Automatic merge from submit-queue (batch tested with PRs 54230, 58100, 57861, 54752). If you want to cherry-pick this change to another branch, please follow the instructions here. |
…861-upstream-release-1.8 Automatic merge from submit-queue. Automated cherry pick of #57861: Use existing subnetwork of forwarding rule Cherry pick of #57861 on release-1.8. #57861: Use existing subnetwork of forwarding rule **Release note**: ```release-note GCE: Allows existing internal load balancers to continue using an outdated subnetwork ```
…861-upstream-release-1.9 Automatic merge from submit-queue. Automated cherry pick of #57861: Use existing subnetwork of forwarding rule Cherry pick of #57861 on release-1.9. #57861: Use existing subnetwork of forwarding rule **Release note**: ```release-note GCE: Allows existing internal load balancers to continue using an outdated subnetwork ```
Fixes #57860
Test Cases:
Clusters using auto network with existence of a manual subnet in same region.
Version 1.7 does not attempt to fill in the subnetwork, so the forwarding rule was created with the correct subnetwork.
Clusters with manual subnets have always and will continue to use the subnet specified in gce.conf.
Clusters with legacy networks have always and will continue to use an empty subnet.
Release note: