feat: SkipMachinePoolModelReconciliation#6325
Conversation
Signed-off-by: Jack Francis <jackfrancis@gmail.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #6325 +/- ##
==========================================
+ Coverage 43.74% 43.82% +0.08%
==========================================
Files 289 291 +2
Lines 25475 25331 -144
==========================================
- Hits 11143 11102 -41
+ Misses 13529 13456 -73
+ Partials 803 773 -30 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Signed-off-by: Jack Francis <jackfrancis@gmail.com>
|
/retest |
There was a problem hiding this comment.
Can you also add a test case to TestMachinePoolScope_NeedsRequeue to teset the new path as well? Something like "should not requeue if an instance VM image does not match the VMSS when SkipMachinePoolModelReconciliation is enabled". Sorry I missed this in the initial review.
Signed-off-by: Jack Francis <jackfrancis@gmail.com>
| proactively replace instances running an older model with new instances (running the latest model). | ||
|
|
||
| This is useful for testing scenarios and for operators who want to manage instance refresh on their own schedule | ||
| without disabling other reconciliation behavior. To enable it, set `EXP_SKIP_MACHINE_POOL_MODEL_RECONCILIATION=true` |
There was a problem hiding this comment.
Where is this environment variable wired? It doesn't look like it's being read in manager.yaml like the other feature gates.
|
|
||
| ### Skipping Model Reconciliation | ||
| - **Feature status:** Experimental (Alpha) | ||
| - **Feature gate:** SkipMachinePoolModelReconciliation=false |
There was a problem hiding this comment.
Should this be SkipMachinePoolModelReconciliation=true or is it indicating the default is false?
What type of PR is this?
What this PR does / why we need it:
This PR adds a SkipMachinePoolModelReconciliation feature gate to disable AzureMachinePool reconciliation and replacement of VMSS VMs that are running a non-latest VMSS model.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
TODOs:
Release note: