Ensure the OpenBao resources land in vault ns even in Workload Cluster (!8428) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Adds ks.spec.targetNamespace: vault to each unit that deploys manifests into the hardcoded vault namespace (via their .metadata.namespace and/or the kustomize namespace transformer) but doesn't declare a targetNamespace (openbao, openbao-set-service-label & vault-secrets), so the workload cluster default of sylva-system namespace) stops overriding it.

We could strip the manifests from openbao, openbao-set-service-label of their .metadata.namespace (and kustomize-units/vault-secrets/kustomization.yaml from its namespace transformer), I just did not do it because such a duplication is present in more places.

Note: The vault-secrets unit generates a PasswordPolicy/sylva-password-policy that is useful for units which can be deployed on workload cluster, like harbor (for its RandomSecret resources in harbor-init), but would also create RandomSecret resources that are likely unused, like for Rancher or Flux WebUI.

#4316

Test coverage

Adding these overrides in the workload clusters allowed for the deployment to complete with success.

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 Jul 06, 2026 by Bogdan-Adrian Burciu

Ensure the OpenBao resources land in vault ns even in Workload Cluster

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports