sylvactl use --save-inventory (!6056) · Merge requests · Sylva-projects / sylva-core

Use sylvactl watch --save-inventory option to collect relevant inventory status. Thanks to this new option of sylvactl we don't have anymore to blindly take the last n lines of sylvactl output.

Example result in https://gitlab.com/sylva-projects/sylva-core/-/jobs/12095017639#L601:

❌ 🔻🔻🔻🔻🔻 sylvactl watch conclusion... 
Command timeout exceeded: Kustomization/sylva-system/management-sylva-units-ready did not became Ready after 1m0s
The following resources were progressing and not ready:
IDENTIFIER                                                                                 STATUS     REASON                  MESSAGE
Kustomization/sylva-system/cluster                                                         InProgress                         Kustomization generation is 1, but latest observed generation is -1
╰┄╴HelmRelease/sylva-system/cluster                                                        Ready                              Resource is Ready
   ├┄╴Cluster/sylva-system/mgmt-2159581301-kubeadm-capd                                    InProgress                         Scaling up control plane to 1 replicas (actual 0)
   ┆  ╰┄╴KubeadmControlPlane/sylva-system/mgmt-2159581301-kubeadm-capd-control-plane       InProgress                         Scaling up control plane to 1 replicas (actual 0)
   ┆     ╰┄╴Machine/sylva-system/mgmt-2159581301-kubeadm-capd-control-plane-54f66          InProgress                         1 of 2 completed
   ┆        ╰┄╴DockerMachine/sylva-system/mgmt-2159581301-kubeadm-capd-control-plane-54f66 InProgress                         0 of 2 completed
   ┆           ╰┄╴┬┄┄[Conditions]
   ┆              ├┄╴Ready                                                                 False      WaitingForBootstrapData 0 of 2 completed
   ┆              ╰┄╴ContainerProvisioned                                                  False      WaitingForBootstrapData
   ╰┄╴KubeadmControlPlane/sylva-system/mgmt-2159581301-kubeadm-capd-control-plane          InProgress                         Scaling up control plane to 1 replicas (actual 0)
      ╰┄╴Machine/sylva-system/mgmt-2159581301-kubeadm-capd-control-plane-54f66             InProgress                         1 of 2 completed
         ╰┄╴DockerMachine/sylva-system/mgmt-2159581301-kubeadm-capd-control-plane-54f66    InProgress                         0 of 2 completed
            ╰┄╴┬┄┄[Conditions]
               ├┄╴Ready                                                                    False      WaitingForBootstrapData 0 of 2 completed
               ╰┄╴ContainerProvisioned                                                     False      WaitingForBootstrapData
❌ 🔺🔺🔺🔺🔺 🔎

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

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 Nov 17, 2025 by Thomas Morin

sylvactl use --save-inventory

CI configuration

Global config for deployment pipelines

Merge request reports