-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Release reserved GCE IP address after ensure completes, irrespective of outcome. #97740
Conversation
Previous behavior was to release the ip only upon success, but it should be released on failure as well. Otherwise, an IP address will be unnecessarily consumed due to an in-error service.
/triage accepted |
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
/approve
/assign @liggitt @andrewsykim |
/approve |
/approve cancel deferring to cloud-provider approvers |
/unassign |
/approve Should this have release notes? |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andrewsykim, MrHohn, prameshj 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 |
Since this is a bug fix, I had not added releases notes. Updated the PR now. |
/priority important-soon |
…40-upstream-release-1.20 Automated cherry pick of #97740: Release reserved GCE IP address after ensure completes.
…40-upstream-release-1.19 Automated cherry pick of #97740: Release reserved GCE IP address after ensure completes.
…40-upstream-release-1.17 Automated cherry pick of #97740: Release reserved GCE IP address after ensure completes.
…40-upstream-release-1.18 Automated cherry pick of #97740: Release reserved GCE IP address after ensure completes.
Previous behavior was to release the ip only upon success, but it should be released
on failure as well. Otherwise, an IP address will be unnecessarily consumed due to an
in-error service.
What type of PR is this?
What this PR does / why we need it:
Prior to this change, the controller behavior was to release the ip only upon success, but it should be released
on failure as well. Otherwise, an IP address will be unnecessarily consumed due to an
in-error service.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: