-
Notifications
You must be signed in to change notification settings - Fork 302
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 "SHARED_LOADBALANCER_VIP" to internal addresses #2735
base: master
Are you sure you want to change the base?
Add "SHARED_LOADBALANCER_VIP" to internal addresses #2735
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: TortillaZHawaii The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @TortillaZHawaii. Thanks for your PR. I'm waiting for a kubernetes 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-sigs/prow repository. |
It looks like it is an issue for existing IP addresses. If an address was reserved before this change trying to reserve it again with .Purpose = "SHARED_LOADBALANCER_VIP" will lead to an error:
Not sure how to resolve it without traffic interruption |
/ok-to-test |
When creating multiple internal forwarding rules for one address we need to use the address with .Purpose = "SHARED_LOADBALANCER_VIP". Otherwise we will receive an
Error syncing load balancer: googleapi: Error 409: IP_IN_USE_BY_ANOTHER_RESOURCE - IP '10.164.0.18' is already being used by another resource
.