Update metal3 to 0.16.0 and capm3 to 1.13.6 / ipam to 1.13.7

What does this MR do and why?

This is a combination of !9418 (closed) and !7940 (closed)

  • CAPM3 v1.12.8 → v1.13.6, IPAM v1.12.7 → v1.13.7
  • SUSE metal3 chart (BMO/Ironic) 0.15.2 → 0.16.0 (BMO 0.12.3 → 0.13.3)
  • sylva-library / sylva-capi-cluster bumped for the CAPM3 v1beta2 API

Why 1.13 and not 1.14 (!7940 (closed))

!7940 (closed) (CAPM3 1.14.1) deploys, but the pivot never completes. CAPM3 1.14 is built against BMO API v0.14. It writes provisioningFailCount into the BMH baremetalhost.metal3.io/status annotation when it pauses BMHs for clusterctl move. The BMO webhook in our SUSE build (0.12.3, and still 0.13.3 in chart 0.16.0) decodes that annotation with DisallowUnknownFields and rejects the patch. The BMHs never get paused, the CAPM3 1.14 block-move annotation is never removed, and clusterctl move fails.

CAPM3 1.13.6 is built against BMO API v0.13.6, which has the same BMH status fields as the BMO 0.13.3 shipped by the SUSE metal3 0.16.0 chart. 1.13 also still uses BMH owner references (no block-move), so pivot.sh needs no change. We can move to 1.14 once SUSE ships a metal3 chart with BMO >= 0.14.

Why the extra changes

  • Bump the metal3 chart together with CAPM3: keeps BMO on the same API minor version that CAPM3 is built against.
  • sylva-library / sylva-capi-cluster (sylva-library!175, sylva-capi-cluster!1138): CAPM3 1.13 makes infrastructure.cluster.x-k8s.io/v1beta2 the storage version. Templates now render the v1beta2 schema: diskFormat, cloudProviderEnabled, prefixesFromPool, bond parameters as a name/value list, and bonds:/vlans: omitted when empty.
  • kustomize-units/capm3 – Metal3DataTemplate CRD patch (temporary): the v1beta2 CRD types bond parameter value as object, which rejects every scalar (miimon: 100, mode: active-backup, ...). The controller passes the raw value through to cloud-init, so we drop the type and get the same behaviour as v1beta1. The op: test guards make the build fail if upstream changes the schema.
  • kustomize-units/capm3 – force-recreate capm3-mutating-webhook-configuration (temporary, upgrades only): 1.13 goes from 9 to 2 defaulting webhooks. The leftover cainjector-owned caBundle entries make Flux's SSA dry-run fail as Invalid, so force lets Flux recreate the object. This can be dropped once no supported upgrade path starts below 1.13.

Depends on:

Related to #4870

Test coverage

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon Meaning Available values
☁️ Infra Provider capd, capo, capm3
🚀 Bootstrap Provider kubeadm (alias kadm), rke2, okd, ck8s
🐧 Node OS ubuntu, suse, na, leapmicro
🛠️ Deployment Options Deployment option list and description
🎬 Pipeline Scenarios Available scenario list and description
🟢 Enabled units Any available units name, by default apply to management and workload cluster. Can be prefixed by mgmt: or wkld: to be applied only to a specific cluster type
🔴 Disabled units Any available units name, by default apply to management and workload cluster. Can be prefixed by mgmt: or wkld: to be applied only to a specific cluster type
🏗️ Target platform Can be used to select specific deployment environment Available platform list and description
🔀 Workload deployment workflow legacy (default; direct workload-cluster apply) or gitops (deploy workload cluster through the GitOps-managed flow)
⚡ Pipeline control autorun, manual or blocking. Can be used to override global config and start a deployment pipeline the required way
  • 🎬 preview ☁️ capd 🚀 kadm 🐧 ubuntu

  • 🎬 preview ☁️ capo 🚀 rke2 🐧 suse

  • 🎬 preview ☁️ capm3 🚀 rke2 🐧 ubuntu

  • ☁️ capd 🚀 kadm 🛠️ light-deploy 🐧 ubuntu

  • ☁️ capd 🚀 rke2 🛠️ light-deploy 🐧 suse

  • ☁️ capo 🚀 rke2 🐧 suse

  • ☁️ capo 🚀 rke2 🐧 leapmicro

  • ☁️ capo 🚀 kadm 🐧 ubuntu 🔀 gitops

  • ☁️ capo 🚀 kadm 🐧 ubuntu 🟢 neuvector,mgmt:harbor

  • ☁️ capo 🚀 rke2 🎬 rolling-update 🛠️ ha 🐧 ubuntu

  • ☁️ capo 🚀 kadm 🎬 wkld-k8s-upgrade 🐧 ubuntu

  • ☁️ capo 🚀 rke2 🎬 rolling-update-no-wkld 🛠️ ha 🐧 suse

  • ☁️ capo 🚀 rke2 🎬 sylva-upgrade 🛠️ ha 🐧 ubuntu

  • ☁️ capo 🚀 rke2 🎬 sylva-upgrade-from-1.6.x 🛠️ ha,misc 🐧 ubuntu

  • ☁️ capo 🚀 rke2 🛠️ ha,misc 🐧 ubuntu

  • ☁️ capo 🚀 rke2|okd 🎬 no-update 🐧 ubuntu|na

  • ☁️ capo 🚀 rke2 🛠️ misc 🐧 ubuntu 🟢 mgmt:harbor 🔴 neuvector

  • ☁️ capo 🚀 rke2 🛠️ ha,misc,openbao 🐧 suse

  • ☁️ capo 🚀 rke2 🐧 suse 🎬 upgrade-from-prev-tag

  • ☁️ capm3 🚀 rke2 🐧 suse

  • ☁️ capm3 🚀 kadm 🐧 ubuntu

  • ☁️ capm3 🚀 rke2 🛠️ external-openbao-no-tls 🐧 ubuntu

  • ☁️ capm3 🚀 rke2 🛠️ external-openbao 🐧 suse

  • ☁️ capm3 🚀 kadm 🛠️ external-openbao,openbao-namespace 🐧 ubuntu

  • ☁️ capm3 🚀 ck8s 🐧 ubuntu

  • ☁️ capm3 🚀 kadm 🎬 rolling-update-no-wkld 🛠️ ha,misc 🐧 ubuntu

  • ☁️ capm3 🚀 rke2 🎬 wkld-k8s-upgrade 🛠️ ha 🐧 suse

  • ☁️ capm3 🚀 kadm 🎬 rolling-update 🛠️ ha 🐧 ubuntu

  • ☁️ capm3 🚀 rke2 🎬 upgrade-from-prev-release-branch 🛠️ ha 🐧 suse

  • ☁️ capm3 🚀 rke2 🛠️ misc,ha 🐧 suse

  • ☁️ capm3 🚀 rke2 🎬 sylva-upgrade 🐧 suse

  • ☁️ capm3 🚀 kadm 🎬 rolling-update 🛠️ ha 🐧 suse

  • ☁️ capm3 🚀 ck8s 🎬 rolling-update 🛠️ ha 🐧 ubuntu

  • ☁️ capm3 🚀 rke2|okd 🎬 no-update 🐧 ubuntu|na

  • ☁️ capm3 🚀 rke2 🐧 suse 🎬 upgrade-from-release-1.5

  • ☁️ capm3 🚀 rke2 🐧 suse 🎬 upgrade-to-main

Global config for deployment pipelines

  • autorun pipelines
  • allow failure on pipelines
  • record sylvactl events

Notes:

  • Enabling autorun will make deployment pipelines to be run automatically without human interaction
  • Disabling allow failure will make deployment pipelines mandatory for pipeline success.
  • if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.

Edited by Thomas Morin

Merge request reports

Loading
Loading