Add a CI test tool for the GitOps managed workload cluster deployment flow (!9103) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

This MR adds .gitlab/ci/scripts/test-gitops-workload-cluster.sh, selected via a new wkld-gitops deployment option (wired into .run-apply-workload in templates-deployments.yml). The legacy apply-workload-cluster.sh flow is unchanged and stays the default.

We can now deploy a workload cluster through the GitOps path , where the cluster is declared as a SylvaWorkloadCluster in a team's own repo

Renders environment-values/workload-clusters/<flavour> with merged ci-deployment-values turns the resulting SylvaUnitsRelease into a SylvaUnitsReleasePreset
Applies that preset in the team's namespace (deletes and re-creates it, since a preset's spec is immutable).
Reconciles the team's repo so its SylvaWorkloadCluster is applied, and picks up the new preset.
Waits for the produced SylvaUnitsRelease's HelmReleaseUpToDate condition, then sylvactl watches on the unit's status.

Should be merged first :

sylva-projects/sylva-elements/ci-tooling/gitops-deployment-repos/team-a-clusters!1 (merged)

sylva-projects/sylva-elements/ci-tooling/gitops-deployment-repos/team-b-clusters!1 (merged)

sylva-projects/sylva-elements/ci-tooling/sample-workload-teams-repo!26 (merged)

sylva-projects/sylva-elements/ci-tooling/gitops-deployment-repos/workload-teams-definitions!1 (merged)

sylva-projects/sylva-elements/ci-tooling/gitops-deployment-repos/team-a-clusters!7 (merged)

sylva-projects/sylva-elements/ci-tooling/gitops-deployment-repos/team-b-clusters!2 (merged)

Depends on : sylva-projects/sylva-elements/ci-tooling/ci-deployment-values!510 (merged)

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 Oct 12, 2026 by Priya Goyal

Add a CI test tool for the GitOps managed workload cluster deployment flow

What does this MR do and why?

Related reference(s)

CI configuration

Global config for deployment pipelines

Merge request reports