Fix and run chainsaw restricted-fields test (!9260) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Fix the the chainsaw Job suite for restricted-fields, as it was not loaded from what we can see in https://sylva-projects.gitlab.io/-/sylva-core/-/jobs/16657407069/artifacts/management-cluster-dump/chainsaw-test/run-chainsaw-tests-78cvh/logs.txt

Loading tests...
- avoid-delete-mgmt-cluster (/tests/avoid-delete-mgmt-cluster)
- avoid-delete-mgmt-cluster (/tests/avoid-delete-mgmt-cluster/..2026_09_22_16_08_42.3228598667)
- deny-cabundle-changes (/tests/deny-cabundle-changes)
- deny-cabundle-changes (/tests/deny-cabundle-changes/..2026_09_22_16_08_42.3650095086)
- disallow-default-namespace (/tests/disallow-default-namespace)
- disallow-default-namespace (/tests/disallow-default-namespace/..2026_09_22_16_08_42.330301456)
- disallow-latest-tag (/tests/disallow-latest-tag)
- disallow-latest-tag (/tests/disallow-latest-tag/..2026_09_22_16_08_42.3417010731)
- ensure-force-cluster-policy (/tests/ensure-force-cluster-policy)
- ensure-force-cluster-policy (/tests/ensure-force-cluster-policy/..2026_09_22_16_08_42.1979507470)
Loading values...
Running tests...
=== RUN   chainsaw

due to patch in kustomize-units/chainsaw-tests/components/restricted-fields/kustomization.yaml targeting the the Job by name:

  - target:
      kind: Job
      name: run-chainsaw-tests

while the Job is actually named run-chainsaw-tests${CHAINSAW_SUFFIX}.
Dropping the name match criteria as other components like disallow-latest-tag target only kind: Job and don't have this problem.

Once loaded, there were problems with the test itself:

Step 0 was denied by RBAC. The runner's ClusterRole couldn't read ValidatingAdmissionPolicies, so we needed to introduce a patch granting get/list/watch on validatingadmissionpolicies and validatingadmissionpolicybindings.
Since pods without a namespace in their manifest went to chainsaw-test, which Flux labels sylva.org/sylva-managed: "true" and VAP/restrict-node-selection-binding skips namespaces with that label, the policy was never checked in the test namespace, so the "must be denied" pod was admitted.
We force the pods in a dedicated namespace via Test.spec.namespace: chainsaw-restricted-fields setting, for which chainsaw suite creates the ns, i.e. dedicated namespace without that label where the policy applies. We make use of !9276 (merged) mechanism to have test_sylva_namespaces_are_labeled test skip any label that has sylva.org/test-namespace: "true" label.
Pod Security rejected the test pods in RKE2 cluster so we added securityContext block the other chainsaw suites use.
Step 2's delete timed out. The kube-system pod is bound to a node that doesn't exist, so no kubelet confirms its deletion. The garbage collector removes it only after about 40–60s, longer than chainsaw's default 20s. We encreased the delete timeout to 90s.

Test coverage

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 Sep 28, 2026 by Bogdan-Adrian Burciu

Fix and run chainsaw restricted-fields test

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports