Circular dependency error when deploying CAPO workload cluster with additional networks (!6845) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Refactors the capo-gateway-validation dependency on capo-orc.

The dependency on capo-orc is now limited to the management cluster only, removing it from the workload cluster to avoid a cyclic dependency.

Tested with SYLVA_CI_VALUES_REVISION: cm-capo-sec

➜  ./tools/serve-crustgather-artifact.sh -j 13006437854 -b
➜  kubectl -n rke2-capo get ks capo-gateway-validation -o jsonpath='{.status.conditions}'                    
[{"lastTransitionTime":"2026-02-05T18:35:32Z","message":"Applied revision: 0.0.0-git-bac49d4d@sha256:2607ea7203c7e879606f92c165f5012c181198da473447157cc487c907d77465","observedGeneration":1,"reason":"ReconciliationSucceeded","status":"True","type":"Ready"},{"lastTransitionTime":"2026-02-05T18:35:32Z","message":"Health check passed in 56.983746ms","observedGeneration":1,"reason":"Succeeded","status":"True","type":"Healthy"}]% 
➜  kubectl -n rke2-capo describe job capo-gateway-validation
Name:             capo-gateway-validation
Namespace:        rke2-capo
Selector:         batch.kubernetes.io/controller-uid=bd1e91fa-f655-40b4-ae5d-83238296d5b7
Labels:           kustomize.toolkit.fluxcd.io/name=capo-gateway-validation
                  kustomize.toolkit.fluxcd.io/namespace=rke2-capo
Annotations:      <none>
Parallelism:      1
Completions:      1
Completion Mode:  NonIndexed
Suspend:          false
Backoff Limit:    1000000
Start Time:       Thu, 05 Feb 2026 18:35:16 +0000
Completed At:     Thu, 05 Feb 2026 18:35:31 +0000
Duration:         15s
Pods Statuses:    0 Active (0 Ready) / 1 Succeeded / 0 Failed

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	`light-deploy`, `dev-sources`, `ha`, `misc`, `maxsurge-0`, `logging`, `no-logging`, `cilium`
🎬	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
🏗️	Target platform	Can be used to select specific deployment environment (i.e `real-bmh` for capm3 )

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

Circular dependency error when deploying CAPO workload cluster with additional networks

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports