You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating many LoadBalancer services, some services may exceed Azure basic LB's FrontendIPConfiguations quota (default is 10). Public IPs are created for all services, but it is not removed after deleting the kubernetes services.
I0202 08:50:13.986196 1 service_controller.go:725] Service has been deleted default/nginx35. Attempting to cleanup load balancer resources
E0202 08:50:13.986573 1 service_controller.go:218] error processing service default/nginx35 (will retry): Expected to find an IP address for service nginx35 but did not
I0202 08:50:13.986618 1 event.go:218] Event(v1.ObjectReference{Kind:"Service", Namespace:"default", Name:"nginx35", UID:"eb4d9e3f-07eb-11e8-bb1d-000d3a19c1da", APIVersion:"v1", ResourceVersion:"3794301", FieldPath:""}): type: 'Normal' reason: 'DeletingLoadBalancer' Deleting load balancer
I0202 08:50:13.986759 1 event.go:218] Event(v1.ObjectReference{Kind:"Service", Namespace:"default", Name:"nginx35", UID:"eb4d9e3f-07eb-11e8-bb1d-000d3a19c1da", APIVersion:"v1", ResourceVersion:"3794301", FieldPath:""}): type: 'Warning' reason: 'DeletingLoadBalancerFailed' Error deleting load balancer (will retry): Expected to find an IP address for service nginx35 but did not
What you expected to happen:
Remove the public IP.
How to reproduce it (as minimally and precisely as possible):
Create more than 10 LoadBalancer services, wait a while for 10 services success, and then remove all services.
Anything else we need to know?:
Environment:
Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:
The text was updated successfully, but these errors were encountered:
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.
Ensure public IP removed after service deleted
**What this PR does / why we need it**:
When creating many LoadBalancer services, some services may exceed Azure basic LB's FrontendIPConfiguations quota (default is 10). Public IPs are created for all services, but it is not removed after deleting the kubernetes services.
This PR fixes the problem.
**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
Fixeskubernetes#59255
**Special notes for your reviewer**:
Should cherry-pick to v1.9.
**Release note**:
```release-note
Ensure Azure public IP removed after service deleted
```
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
When creating many LoadBalancer services, some services may exceed Azure basic LB's FrontendIPConfiguations quota (default is 10). Public IPs are created for all services, but it is not removed after deleting the kubernetes services.
What you expected to happen:
Remove the public IP.
How to reproduce it (as minimally and precisely as possible):
Create more than 10 LoadBalancer services, wait a while for 10 services success, and then remove all services.
Anything else we need to know?:
Environment:
kubectl version
):uname -a
):The text was updated successfully, but these errors were encountered: