remove pdb-minavailable-check Kyverno policy (!7046) · Merge requests · Sylva-projects / sylva-core

Proposal following up the proposal done in #3660

This MR deletes the pdb-minavailable-check Kyverno admission policy, keeping only the pdb-minavailable-audit background/audit policy which tests the same PDB misconfiguration case.

The idea is to avoid having create/update operations on Deployments and StatefulSets go through the Kyverno admission webhook, which introduces a fragility point because of scenarios where Kyverno webhook would not be available.

Having only the audit background policy will not make a practical difference for the mgmt cluster (we have a CI job that will fail if the audit policy triggers).

For workload clusters there won't be a difference either, since none of the two policies is enabled today in workload clusters. Also it's not obvious that for workload clusters we would really want to block a CNF or application deployment because of a misconfigured PDB. When !3352 will land, ops will have to watch out for policy reports to catch the misconfiguration.

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
🔴	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 (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.

Edited Feb 25, 2026 by Thomas Morin

remove pdb-minavailable-check Kyverno policy

CI configuration

Global config for deployment pipelines

Merge request reports