-
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
🌱 Reconcile topology only when necessary #11605
🌱 Reconcile topology only when necessary #11605
Conversation
/test |
@fabriziopandini: The
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/test pull-cluster-api-e2e-main |
/test pull-cluster-api-e2e-main |
/lgtm /assign @chrischdi |
LGTM label has been added. Git tree hash: 08906cafbd015fe1ea2927c50adafa5fd4a0f90a
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chrischdi 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 |
@fabriziopandini: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
/hold |
/lgtm |
LGTM label has been added. Git tree hash: 66b39240b5b802b5ca6798642c21e916e54d1c20
|
Did some local testing, all good /hold cancel |
What this PR does / why we need it:
The topology controller is responsible to enforce the desired state of the cluster, and it does this ensuring that the spec of the cluster itself and the spec of the dependant objects like e.g. Machine Deployment is consistent with what defined in the ClusterClass.
That means that this controller should not care of changes to objects status (or at least to a subset of changes in status).
This PR introduces two predicates starting to drop reconcile events when the changes are not relevant for the topology controller
/area cluster