Skip to content

feat(kyverno): unregister the classic auto-vpa ClusterPolicy #5132

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
Oct 20, 2026
+7 −1
Merged

feat(kyverno): unregister the classic auto-vpa ClusterPolicy #5132

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
8 changes: 7 additions & 1 deletion k8s/bases/infrastructure/cluster-policies/kustomization.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,13 @@ resources:
- best-practices/add-recommended-labels.yaml
- best-practices/add-resource-defaults.yaml
- best-practices/add-security-context.yaml
- best-practices/auto-vpa.yaml
# best-practices/auto-vpa.yaml is deliberately NOT registered: it is step 1
# of the shared catalog's two-reconcile move to its GeneratingPolicy form
# (devantler-tech/kyverno-policies#1). Removing the classic policy deletes
# the VPAs it generated; the GeneratingPolicy form is registered in a later
# revision, once no `generate.kyverno.io/policy-name=auto-vpa` VPA remains,
# so the two forms never run at once. The file stays, still tested, as the
# rollback form until that move is complete.
- best-practices/audit-privileged-rbac.yaml
- best-practices/disable-default-sa-automount.yaml
- best-practices/disallow-latest-tag.yaml
Expand Down
Loading