[backport-1.6] optimizations to reduce sylva-units Helm chart CPU/mem requirements (!7522) · Merge requests · Sylva-projects / sylva-core

This MR is a backport of:

We usually do not necessarily backport optimization. The motivation for backporting these is that without these, the CPU and memory consumption required to render the sylva-units Helm chart is huge, with an observed impact on mgmt node dimensioning ; and both CPU and mem are much lower and very reasonable with these improvements. The long render time is also impacting user experience and dev experience when iterating on MRs.

Results (benchmark is helm template with the values of my dev environment mgmt cluster):

before: 17s processing time and memory peak at 995Mi
after: 3s processing time and memory peak at 104Mi

So the improvement is, on this benchmark, approximately:

6 times faster 🎉
10 times less memory used 🎉

Comparison with early March code

For reference, in early March (before integrating a first optimization; see !7084 (merged)), the numbers with the same benchmark were:

25s
2591 Mi

So after merging this MR, compared to what we had beginning of March in release-1.6, we'll have improved render time by a factor 8, and memory usage by a factor of 25.

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
🔴	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 (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 Apr 10, 2026 by Thomas Morin

[backport-1.6] optimizations to reduce sylva-units Helm chart CPU/mem requirements

Comparison with early March code

CI configuration

Global config for deployment pipelines

Merge request reports