Add dependency on vault-init for openbao-set-service-label unit, in order to avoid timeouts (!6713) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

As observed in the CI run, there are some corner cases where the openbao-set-service-label Kustomization would time out:

unit Kustomization/openbao-set-service-label did not became ready after 5m0s
Details on Kustomization/openbao-set-service-label and related resources:
IDENTIFIER                                           STATUS     REASON               MESSAGE
Kustomization/sylva-system/openbao-set-service-label InProgress                      Kustomization generation is 1, but latest observed generation is -1
╰┄╴┬┄┄[Conditions]
   ├┄╴Reconciling                                    True       ProgressingWithRetry Detecting drift for revision 0.0.0-git-d68ce89b@sha256:fef3e3feaf2cd421e398c18f3509b57cdea300ef61e82e4f762f3ca68bf7418b with a timeout of 30s
   ╰┄╴Ready                                          False      ReconciliationFailed Policy/vault/openbao-set-service-label not found: namespaces "vault" not found

This is caused by how we are now deploying the vault namespace, as a follow-up from !6272 (merged).

This MR simply adds a dependency on the vault-init unit, on the openbao-set-service-label unit, in order to avoid failures.

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.

Add dependency on vault-init for openbao-set-service-label unit, in order to avoid timeouts

What does this MR do and why?

CI configuration

Global config for deployment pipelines

Merge request reports