-
Notifications
You must be signed in to change notification settings - Fork 406
Stop apiimporter, syncer, heartbeat from fighting over the Ready condition #864
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
Conversation
6075c80
to
5bda7f7
Compare
5bda7f7
to
243f2b3
Compare
Give each controller its own condition and make them responsible for setting Ready by accounting for all conditions via conditions.SetSummary Signed-off-by: Christopher Sams <[email protected]>
243f2b3
to
9d381ac
Compare
Signed-off-by: Christopher Sams <[email protected]>
Signed-off-by: Christopher Sams <[email protected]>
@marun @imjasonh how does this look to you? For background/additional context: the conditions library we're using (from Cluster API) went through extensive R&D, settling on the use of SetSummary to summarize a resource's Ready condition. It's a good practice to follow, and even if we only currently have a single condition that represents Ready, for future-proofing, we should choose a unique name for that condition, and have it flow into Ready via SetSummary. |
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.
This looks like a good change, thanks! 👍
Stop apiimporter, syncer, heartbeat from fighting over the Ready condition
Give each controller its own condition and make heartbeat manager responsible for setting
Ready
by accounting for all conditions viaconditions.SetSummary
Update the namespace scheduler to depend on total readiness.
Fixes #865