-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🐛 fix cluster deletion in the in-memory API server #8818
🐛 fix cluster deletion in the in-memory API server #8818
Conversation
/hold Adding some cleanup in reconcileDelete functions |
a8e34c0
to
ff73bab
Compare
/hold cancel |
@killianmuldoon PTAL |
ff73bab
to
fa1cd34
Compare
/retest |
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
/hold
Pending passing of tests
LGTM label has been added. Git tree hash: 68fa487a2e3d536df9c64520dd1dad8edfddba83
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: killianmuldoon 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 |
/hold cancel |
/area provider/infrastructure-in-memory |
What this PR does / why we need it:
This PR makes the cluster deletion to work when using the in-memory API server; the issue was caused by the node drainer using application/json to delete pods (while the controller runtime client uses protobuf)
Rif #8814