Remove user and group from chainsaw tests (!8821) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

The chainsaw job pinned runAsUser/runAsGroup to 65532, which is the chainsaw image's own default user, redundant on RKE2/kubeadm, and rejected on OKD where the restricted-v2 SCC only permits UIDs from the range allocated to the namespace. This MR is dropping the pin to make the SCC assign a valid UID on OpenShift/OKD while leaving the effective UID unchanged everywhere else.

Closes #4474 (closed)

Test coverage

Tested on a RKE2 management cluster with an OKD workload cluster.

On the management cluster:

kubectl get po -n chainsaw-test run-chainsaw-tests-8zgsk -o yaml | grep -i user -A 5
    user:
      linux:
        gid: 65532
        supplementalGroups:
        - 65532
        uid: 65532

On the OKD workload cluster:

kubectl get po -n chainsaw-test -o yaml | grep -i user -A 5
      user:
        linux:
          gid: 0
          supplementalGroups:
          - 0
          - 1000690000

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 Aug 12, 2026 by Dragos Gerea

Remove user and group from chainsaw tests

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports