-
Notifications
You must be signed in to change notification settings - Fork 170
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
Drop SyncSets check #3723
Drop SyncSets check #3723
Conversation
/azp run ci |
Azure Pipelines successfully started running 1 pipeline(s). |
9435958
to
cb566c4
Compare
/azp run ci |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Change and motivation LGTM.
I'm curious if we should still keep an explicit SyncSets ready check at the end of our install process, just to make sure we don't have any WIP before we hand the cluster over to the user, but that can be introduced whenever we actually start using SyncSets.
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!
Which issue this PR addresses:
Fixes: https://issues.redhat.com/browse/ARO-7787
What this PR does / why we need it:
This PR drops the sync sets check from
IsClusterDeploymentReady
.Monitoring of SyncSets will come as part of it's own monitoring in the future and since we have no SyncSets at present there is no temporary gap.
Test plan for issue:
Tested locally using the dev Hive