[release-1.6] let cluster-machines-ready work on a Sylva 1.7 CAPI 1.12 mgmt cluster (!9109) · Merge requests · Sylva-projects / sylva-core

Context: need to keep the ability to operate Sylva 1.6 workload clusters on a Sylva 1.7 management cluster

Problem statement (#4570 (closed)/sylva-projects#120): when cluster-machines-ready, instantiated from a Sylva 1.6 workload clusters context (and written for CAPI 1.10 / v1beta1) runs on Sylva 1.7 management on which CAPI 1.12 CRDs are installed (v1beta2) -- and it breaks because what it expects in the status does not exist.

The "idiomatic" way to resolve this kind of question in the Kubernetes ecosystem is to rely on apiVersion to ensure backwards compatibility: the client (here cluster-machines-ready) asks for the specific apiVersion that it wants (here v1beta1), and the CRD controller, when needed provides an API conversion webhook to translate whatever is most current into the version that the client wants.

This approach is used in this MR for MachineDeployments, for which the CAPI controller provides a clean conversion (the v1beta1 served when converting from the v1beta2 has the status fields that cluster-machines-ready needs). To do this we simply do kubectl wait machinedeployment.v1beta1.cluster.x-k8s.io instead of kubectl wait machinedeployment.

For the CAPI control plane resource, this approach would have been nice as well. But unfortunately for rke2 this does not work (the v1beta1 served when converting from the v1beta2 is missing most of the status fields that cluster-machines-ready needs). ** In this MR, I hence opted for a less elegant path**: the code tests which field is found in status and when the v1beta1 field isn't found, uses the closest alternative found in v1beta2 (the field that we use in release-1.7/main version of cluster-machines-ready).

💡 the CP change and the MD change are done in two separate commits

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
⚡	Pipeline control	`autorun`, `manual` or `blocking`. Can be used to override global config and start a deployment pipeline the required way

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 Sep 11, 2026 by Thomas Morin

[release-1.6] let cluster-machines-ready work on a Sylva 1.7 CAPI 1.12 mgmt cluster

CI configuration

Global config for deployment pipelines

Merge request reports