-
Notifications
You must be signed in to change notification settings - Fork 178
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
Only perform machineconfig reconciliation during OpenShift upgrades #3473
Conversation
40629c1
to
e7a374f
Compare
/azp run ci, e2e |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run ci, e2e |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run ci, e2e |
Azure Pipelines successfully started running 2 pipeline(s). |
Please rebase pull request. |
/azp run ci, e2e |
Pull request contains merge conflicts. |
070d418
to
a1c5985
Compare
/azp run ci, e2e |
Azure Pipelines successfully started running 2 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.
I trust the tests here, thanks Amber.
wantConditions: defaultConditions, | ||
}, | ||
{ | ||
name: "MachineConfigPool reconciliation does not existing DNS MachineConfigs when not updating", |
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.
nit: grammar, probably "does not update existing"?
… if cluster is upgrading
6ce74fc
to
761c4fb
Compare
/azp run ci, e2e |
Azure Pipelines successfully started running 2 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.
I finished QA'ing and it was working fine. Approved from my standpoint as well.
Which issue this PR addresses:
Fixes https://issues.redhat.com/browse/ARO-6250
What this PR does / why we need it:
Only performs MachineConfig reconciliation when OpenShift is being upgraded.
Test plan for issue:
Unit tests + E2E should cover it.
Is there any documentation that needs to be updated for this PR?
Yes, SOPs for manually forcing reconciliation
How do you know this will function as expected in production?
E2E + testing should cover known cases, but might require further testing.