Skip to content

revert(kyverno): drop temporary background-controller v=4 verbosity #2400

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
devantler merged 1 commit into from
Jul 3, 2026
Merged

revert(kyverno): drop temporary background-controller v=4 verbosity #2400

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 0 additions & 10 deletions k8s/bases/infrastructure/controllers/kyverno/helm-release.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -167,16 +167,6 @@ spec:
app.kubernetes.io/instance: kyverno
backgroundController:
replicas: ${kyverno_background_replicas:=1}
# TEMPORARY diagnostic for #2392: the drain-autoscale-node-storage
# mutate-existing retrofit generates zero UpdateRequests and logs
# NOTHING at the default v=2 -- every rejection path in the policy
# controller's ApplyBackgroundChecks is V(4)-only, so the failure is
# silent by construction. extraArgs render AFTER the features-derived
# --v=2 and klog is last-wins, so this raises verbosity to 4 on this
# controller only (admission/cleanup/reports stay at v=2). Revert once
# #2392 is root-caused.
extraArgs:
v: 4
# The chart auto-enables this controller's PDB whenever replicas > 1 and
# defaults it to minAvailable: 1 -- the exact shape validate-pdb-drain-safe
# flags. Pin the drain-safe house pattern (#1880/#1882) instead. The
Expand Down