OKD on CAPO (!7518) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

OKD/OCP on CAPO (OpenStack): fully automated workload cluster deployment with zero manual steps.

Key features:

Auto-allocated API and Ingress VIPs (auto-select or user-provided) via Heat stack
ENABLE_METAL3=false toggle for assisted-service on CAPO (no Metal3 CRDs required)
Privileged SCC binding for cinder-csi on OKD workload clusters
Boilerplate template for OKD-on-CAPO workload clusters

Changes:

charts/sylva-units/values.yaml — postBuild substitutions (ENABLE_METAL3, DISABLED_HOST_VALIDATIONS), set-only-if for ingressVIP valuesFrom (only for cabpoa+capo, avoids schema breakage on non-OKD)
kustomize-units/openshift-assisted-installer/assisted-service-config.yaml — substitution variables for ENABLE_METAL3 and DISABLED_HOST_VALIDATIONS
kustomize-units/capo-cluster-resources/heat-stack/stack-cluster-resources.yaml — ingress-port Heat resource with auto-allocation or user-provided
kustomize-units/openshift-security-context-constraints/components/cinder-csi/ — SCC ClusterRoleBinding for cinder-csi on OKD
environment-values/workload-clusters/okd-capo/ — boilerplate template for OKD-on-CAPO workload clusters

Dependencies:

sylva-capi-cluster branch vj-okd-capo (CABPOA ignition host entries, CAPO support)
MCE 2.17.20260521

Align OKD provider with CAPO #1961 (closed)
sylva-capi-cluster: vj-okd-capo branch on gitlab.com/sylva-projects/sylva-elements/helm-charts/sylva-capi-cluster.git.
sylva-capi-cluster MR link sylva-projects/sylva-elements/helm-charts/sylva-capi-cluster!1046 (merged)
Upstream PRs required (already merged in main): openshift/assisted-service#9933, openshift-assisted/cluster-api-provider-openshift-assisted#536

Test coverage

Full e2e: 3 CP nodes, OKD 4.20.0, 100% install completed, cinder-csi healthy
MCE 2.17 with zero private images
Tested OpenStack CAPO provider network

Note: CI helm-schema-validation failure is expected — the schema depends on sylva-capi-cluster branch vj-okd-capo which is not yet merged into the branch CI uses for schema generation.

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

OKD on CAPO

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports