make root-dependency-check faster (!9593) · Merge requests · Sylva-projects / sylva-core

In the context of #4832 (closed), I realized that we could improve how root-dependency-check runs.

Because of the -n1 -P500 setting for xargs we parallelize too much: if you have 200 Kustomizations, the script instantly spawns 200 kubectl processes, and this puts a heavy burden on the system.

I think that what we should improve this by spawning less kubectl processes in parallel.

Doing more tests, I find that we would have a better balance with -n 5 -P50:

each kubectl waits on 5 Kustomizations
never more than 50 kubectl commands are run

Before:

$ time (kubectl get Kustomizations -o name -l sylva-units/root-dependency-wait | xargs -n1 -P500 kubectl wait --timeout 30s --for=jsonpath="{.metadata.annotations.sylva-units-helm-revision}=1838" >/dev/null)
     50,85s user 20,67s system 802% cpu 8,913 total
                                        ^^^^^^^^^^^

After:

$ time (kubectl get Kustomizations -o name -l sylva-units/root-dependency-wait | xargs -n5 -P50 kubectl wait --timeout 30s --for=jsonpath="{.metadata.annotations.sylva-units-helm-revision}=1838" >/dev/null)
     9,85s user 3,70s system 477% cpu 2,837 total
                                      ^^^^^^^^^^^

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

make root-dependency-check faster

CI configuration

Global config for deployment pipelines

Merge request reports