Pass Management CA cert content to Workload cluster (!6339) · Merge requests · Sylva-projects / sylva-core

This MR reintroduces !5335 (merged) in a different way, to address the problems described in #3259 (closed)

Credits goes to @amit5.kumar for doing the heavy lifting on this feature. This MR is only the final piece.

The approach taken is the one I proposed in #3259 (comment 2942532727)

It also extends the functionality a bit, by including extra cert coming from sylva-units "external_certificates.cacert" in the scope of what is passed to the workload clusters.

What this MR does:

ensure that the ca-key-pair Secret is directly present in each workload cluster ns as a Secret
- this is done by leveraging the fact that we already have the eso-store-k8s-cert-manager ClusterSecretStore making it possible to read the ca-key-pair Secret from a workload cluster namespace with an ExternalSecret

have the cluster unit directly read from this Secret, ie. simplified this gives something like:

units:
  #...
  cluster:
    helmrelease_spec:
      valuesFrom:
        - kind: Secret
          name: ca-key-pair
          targetPath: additional_ca_delayed_update

This gives the following information flow:

flowchart LR
    ca-key-pair["ca-key-pair/cert-manager<br>Secret"] -->|ExternalSecret| ca-key-pair-wkld["ca-key-pair/wkld-ns<br>Secret"]
    ca-key-pair-wkld -->|cluster HelmRelease<br>valuesFrom| cluster["additional_ca_delayed_update"]

References

Closes #1892 (closed)

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 Dec 10, 2025 by Thomas Morin

Pass Management CA cert content to Workload cluster

References

CI configuration

Global config for deployment pipelines

Merge request reports