Bump Azure Service Operator to v2.18.0#6390
Conversation
|
Skipping CI for Draft Pull Request. |
|
[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 |
|
/test pull-cluster-api-provider-azure-apiversion-upgrade |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #6390 +/- ##
=======================================
Coverage 44.06% 44.07%
=======================================
Files 289 289
Lines 25383 25382 -1
=======================================
+ Hits 11185 11187 +2
+ Misses 13422 13419 -3
Partials 776 776 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
/hold We need to do one ASO minor bump per CAPZ minor bump in order to have the upgrade path work. So this needs to wait until CAPZ 1.26. |
What this PR does / why we need it:
Bumps Azure Service Operator from v2.17.0 to v2.18.0.
v2.18.0 removes the
containerservice/v1api20231001andv1api20230201API versions, so this PR migrates CAPZ's stable managed-cluster/agent-pool alias tov1api20250801(the existing hub) and drops thev1api20230201scheme registration. It also adds a stored-version migration formanagedclusters/managedclustersagentpools(stalev1api20231001storage), since early CAPZ-bundled ASO used that as the storage version.Note: ASO must be upgraded one minor at a time, so a release carrying ASO v2.17.0 should ship before/independently of this one.
Special notes for your reviewer:
Targets v2.18.0 (not later) because v2.19.0 additionally removes
v1api20240402preview, which CAPZ still uses.Release note: