Open TortillaZHawaii opened 4 days ago
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: TortillaZHawaii Once this PR has been reviewed and has the lgtm label, please assign bowei for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
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 /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
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:
[manager.go:226] "Address reserve error" logger="Other controllers.L4Controller.L4Handler.AddressManager" serviceKey="default/hello-service" syncId=1608326150 err="googleapi: Error 409: IP_IN_USE_BY_ANOTHER_RESOURCE - IP '10.164.0.13' is already being used by another resource."
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
.