-
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
🐛 Stop adding parent object owner reference for MachineHealthChecks in managed topologies #6660
🐛 Stop adding parent object owner reference for MachineHealthChecks in managed topologies #6660
Conversation
/test pull-cluster-api-e2e-full-main |
3a67cad
to
26711a8
Compare
26711a8
to
20c496b
Compare
/assign @killianmuldoon @fabriziopandini |
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
20c496b
to
188c1e0
Compare
…of ControlPlanes in topology
188c1e0
to
775707a
Compare
Discussed the PR with Killian and Fabrizio. We decided to drop the owner reference for MHC entirely as they don't seem to be necessary |
/test pull-cluster-api-e2e-full-main |
@sbueringer I updated PR title and description to keep track of the discussion outcomes |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini 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 |
What this PR does / why we need it:
While testing the new release we recognized that we can simplify how we managed MachineHealthChecks in managed topologies by stopping adding parent object owner reference
According to the discussion, we can rely on MHC controller to set the ownerRef to the Cluster, thus ensuring the proper cleanup of the objects during deletion.
Also the order of operations when adding/removing MD ensures no orphan MHC will be left around in a Cluster.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #