-
Notifications
You must be signed in to change notification settings - Fork 303
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
Garbage collect NEGs in to-be-deleted state. #2750
base: master
Are you sure you want to change the base?
Conversation
* Existing NEG GC will always delete all GCE NEGs in NEG CR. With multi-subnet cluster enabled, we could do partial deletions, only on to-be-deleted NEGs.
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: sawsa307 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 |
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.
An initial look here makes me wonder: "Are we forcing this new pattern of deleting NEGs into our existing flow?"
More precisely, the code right now handles the deletion of the SvcNEG and ALL of it's related NEGs. The part here where we also have to handle the deletion of the SvcNEG itself also adds other complications.
What we want to add now is the ability to just deleted targeted NEGs which have a specific state right? Have we thought about doing this in it's own piece of code? Would that be more easier or do we think that has it's own problems?
/assign @swetharepakula
/assign @gauravkghildiyal