-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
KCP: Consider reconciling on Pod events #11745
Comments
/triage accepted |
/help This requires some research about how to avoid too many reconciles + scale tests. |
@chrischdi: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed 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. |
/assign |
Hi @sbueringer But this change I could not find in KCP |
The change in KCP was this here: Please note also the following:
So its not just about start watching and emitting events for this pods. |
Thank @chrischdi sharing details
sure will check this |
We recently changed KCP to use a cached client to retrieve the Pods we care about.
This means we already have informers for Pods of workload clusters.
I'm wondering if we should also trigger reconciles if these Pods change (similar to how we watch on Node events in the Machine controller).
Pro
Con
cluster-api/controlplane/kubeadm/internal/controllers/controller.go
Line 253 in d934125
The text was updated successfully, but these errors were encountered: