Skip to content

Pin the kyverno pod-security policies to a commit and put it in the cached file name #762

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
cert-manager-prow merged 2 commits into from
Sep 30, 2026
Merged

Pin the kyverno pod-security policies to a commit and put it in the cached file name #762

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f40667a
Pin kyverno pod-security policies to release-1.19
wallrj-cyberark Sep 29, 2026
ad9e064
Pin the kyverno policies commit and put it in the cached file name
wallrj Sep 29, 2026
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
25 changes: 21 additions & 4 deletions modules/helm/helm.mk
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,8 +128,25 @@ shared_verify_targets += verify-helm-unittest
$(bin_dir)/scratch/kyverno:
@mkdir -p $@

$(bin_dir)/scratch/kyverno/pod-security-policy.yaml: | $(NEEDS_KUSTOMIZE) $(bin_dir)/scratch/kyverno
@$(KUSTOMIZE) build https://github.com/kyverno/policies/pod-security/enforce > $@
# The commit of kyverno/policies to build the pod-security policies from.
# Pinned because https://github.com/kyverno/policies/pull/1544 deleted pod-security/
# from main; it was superseded by the CEL policies in pod-security-vpol/, see
# https://github.com/kyverno/policies/issues/1543.
#
# This is the tip of the release-1.19 branch, one of the last commits that still
# has pod-security/. The branch name does not matter: the pod-security/ bundle is
# identical on every release branch from release-1.12 to release-1.19, and each
# policy declares kyverno 1.6.0 as its minimum version. The release branches are
# snapshots for the kyverno.io website, not compatibility boundaries. So this
# does not need to change when the kyverno tool in modules/tools is bumped.
kyverno_policies_version := ef9843f08d25b3555fe69616f8612c9f915af5d4

# The version is part of the file name, so a change to it builds a new file
# instead of reusing a stale cached one.
kyverno_policy_file := $(bin_dir)/scratch/kyverno/pod-security-policy-$(kyverno_policies_version).yaml

$(kyverno_policy_file): | $(NEEDS_KUSTOMIZE) $(bin_dir)/scratch/kyverno
@$(KUSTOMIZE) build "https://github.com/kyverno/policies/pod-security/enforce?ref=$(kyverno_policies_version)" > $@

# Extra arguments for kyverno apply.
kyverno_apply_extra_args :=
Expand Down Expand Up @@ -168,9 +185,9 @@ endif
## security policy rules.
##
## @category [shared] Generate/ Verify
verify-pod-security-standards: $(helm_chart_archive) $(bin_dir)/scratch/kyverno/pod-security-policy.yaml | $(NEEDS_KYVERNO) $(NEEDS_HELM)
verify-pod-security-standards: $(helm_chart_archive) $(kyverno_policy_file) | $(NEEDS_KYVERNO) $(NEEDS_HELM)
@$(HELM) template $(helm_chart_archive) $(INSTALL_OPTIONS) \
| $(KYVERNO) apply $(bin_dir)/scratch/kyverno/pod-security-policy.yaml \
| $(KYVERNO) apply $(kyverno_policy_file) \
$(kyverno_apply_extra_args) \
--resource - \
--table
Expand Down
Loading