DirectorySecurity AdvisoriesPricing
Sign in
Directory
kyverno-policies logoHELM

kyverno-policies

Helm chart
Last changed
Request a free trial

Contact our team to test out this Helm chart and related images for free. Please also indicate any other images you would like to evaluate.

Overview
Chart tags
Default values
Chart metadata
Images

Tag:
Compare:

1
# -- Policy kind (`ClusterPolicy`, `Policy`)
2
# Set to `Policy` if you need namespaced policies and not cluster policies.
3
# Only used when `policyType` is `ClusterPolicy` (the legacy kyverno.io types);
4
# with the default `policyType: ValidatingPolicy` cluster-wide CEL policies are installed.
5
policyKind: ClusterPolicy
6
7
# -- Policy engine type (`ClusterPolicy`, `ValidatingPolicy`)
8
# `ValidatingPolicy` installs CEL-based policies (policies.kyverno.io, requires Kyverno 1.17+).
9
# Set to `ClusterPolicy` to keep installing the legacy kyverno.io policy types,
10
# which are deprecated and will be removed in a future release
11
# (see https://kyverno.io/docs/guides/migration-to-cel/).
12
policyType: ValidatingPolicy
13
14
# -- Pod Security Standard profile (`baseline`, `restricted`, `privileged`, `custom`).
15
# For more info https://kyverno.io/policies/pod-security.
16
podSecurityStandard: baseline
17
18
# -- Pod Security Standard severity (`low`, `medium`, `high`).
19
podSecuritySeverity: medium
20
21
# -- Define podSecuritySeverity overrides for specific policies.
22
# Override the global `podSecuritySeverity` with an individual severity for individual policies.
23
# An empty string per-policy entry suppresses the annotation entirely.
24
podSecuritySeverityByPolicy: {}
25
# disallow-host-path: high
26
# disallow-privileged-containers: high
27
28
# -- Policies to include when `podSecurityStandard` is `custom`.
29
podSecurityPolicies: []
30
31
# -- Enable the Kubernetes Pod Security Admission relaxation for user namespace pods
32
# for ValidatingPolicy templates only.
33
# When `true`, the `disallow-proc-mount` (Baseline), `require-run-as-nonroot` and
34
# `require-run-as-non-root-user` (Restricted) ValidatingPolicies skip Pods that explicitly
35
# set `spec.hostUsers` to `false`. A Pod that omits `hostUsers` or sets it to `true` is
36
# always checked. The Restricted `disallow-proc-mount-strict` ValidatingPolicy never
37
# relaxes, and neither does `disallow-proc-mount` when the Restricted profile is installed.
38
# This setting has no effect on legacy `ClusterPolicy` templates.
39
podSecurityUserNamespaces: false
40
41
# -- Additional policies to include from `other`.
42
includeOtherPolicies: []
43
# - require-non-root-groups
44
45
# -- Additional policies to include from `restricted`.
46
includeRestrictedPolicies: []
47
# - require-run-as-non-root-user
48
49
# -- Additional custom policies to include.
50
customPolicies: []
51
# - apiVersion: kyverno.io/v1
52
# kind: ClusterPolicy
53
# metadata: # metadata
54
# spec: # spec
55
56
# -- API server behavior if the webhook fails to respond ('Ignore', 'Fail')
57
# For more info: https://kyverno.io/docs/policy-types/cluster-policy/policy-settings/
58
failurePolicy: Fail
59
60
# -- Validation failure action (`Audit`, `Enforce`).
61
# For more info https://kyverno.io/docs/policy-types/cluster-policy/validate.
62
validationFailureAction: Audit
63
64
# -- Define validationFailureActionByPolicy for specific policies.
65
# Override the defined `validationFailureAction` with a individual validationFailureAction for individual Policies.
66
validationFailureActionByPolicy: {}
67
# disallow-capabilities-strict: Enforce
68
# disallow-host-path: Enforce
69
# disallow-host-ports: Enforce
70
71
# -- Define validationFailureActionOverrides for specific policies.
72
# The overrides for `all` will apply to all policies.
73
validationFailureActionOverrides:
74
all: []
75
# all:
76
# - action: Audit
77
# namespaces:
78
# - ingress-nginx
79
# disallow-host-path:
80
# - action: Audit
81
# namespaces:
82
# - fluent
83
84
# -- Default audit annotations applied to all ValidatingPolicy policies (policyType: ValidatingPolicy only).
85
# Map of annotation key to CEL valueExpression. Audit annotations are recorded in the API server audit log.
86
# For more info https://kyverno.io/docs/policy-types/validating-policy/#using-auditannotations-to-add-custom-data
87
auditAnnotations: {}
88
# policy-evaluated-by: "'kyverno-policies-helm'"
89
90
# -- Define audit annotations for specific ValidatingPolicy policies (policyType: ValidatingPolicy only).
91
# Per-policy entries override defaults when they share the same key.
92
auditAnnotationsByPolicy: {}
93
# disallow-host-path:
94
# violation-details: >-
95
# has(object.spec.volumes) ? 'hostPath volumes found: ' + object.spec.volumes.filter(v, has(v.hostPath)).map(v, v.name).join(', ') : 'no volumes'
96
97
# -- Validate already existing resources.
98
# For more info https://kyverno.io/docs/policy-types/.
99
validationAllowExistingViolations: true
100
101
# -- Exclude resources from individual policies (policyType: ClusterPolicy only).
102
# Policies with multiple rules can have individual rules excluded by using the name of the rule as the key in the `policyExclude` map.
103
# NOTE: This setting only applies when policyType is set to ClusterPolicy. For ValidatingPolicy, use vpolExclude/vpolExcludeByPolicy instead.
104
policyExclude: {}
105
# # Exclude resources from individual policies
106
# disallow-host-path:
107
# all:
108
# - resources:
109
# kinds:
110
# - Pod
111
# namespaces:
112
# - fluent
113
# # Policies with multiple rules can have individual rules excluded
114
# adding-capabilities-strict:
115
# any:
116
# - resources:
117
# kinds:
118
# - Pod
119
# namespaces:
120
# - kube-system
121
122
# -- Default excludes applied to ALL ValidatingPolicy policies (policyType: ValidatingPolicy only).
123
# NOTE: This setting only applies when policyType is set to ValidatingPolicy. For ClusterPolicy, use policyExclude instead.
124
# Supports the following optional keys:
125
# excludeResourceRules: list of Kubernetes NamedRuleWithOperations (native VAP excludes)
126
# excludeNamespaces: list of namespace names to exclude (generates CEL matchCondition)
127
# excludeSubjects: list of subjects to exclude (generates CEL matchCondition)
128
# matchConditions: list of CEL matchConditions for advanced filtering (passthrough of custom condition)
129
# Per-policy overrides via vpolExcludeByPolicy replace these defaults entirely for that policy.
130
vpolExclude: {}
131
# excludeNamespaces:
132
# - kube-system
133
# excludeSubjects:
134
# - kind: Group
135
# name: system:masters
136
137
# -- Per-policy excludes for individual ValidatingPolicy policies (policyType: ValidatingPolicy only).
138
# When set for a policy, it completely replaces the global vpolExclude defaults for that policy.
139
# NOTE: This setting only applies when policyType is set to ValidatingPolicy. For ClusterPolicy, use policyExclude instead.
140
# Each policy name maps to an object with the same keys as vpolExclude.
141
vpolExcludeByPolicy: {}
142
# disallow-host-path:
143
# excludeResourceRules:
144
# - apiGroups:
145
# - ""
146
# apiVersions:
147
# - v1
148
# operations:
149
# - CREATE
150
# - UPDATE
151
# resources:
152
# - pods
153
# # optional - exact resource names to exclude
154
# resourceNames:
155
# - specific-pod-name
156
# excludeNamespaces:
157
# - kube-system
158
# - monitoring
159
# excludeSubjects:
160
# - kind: Group
161
# name: system:masters
162
# - kind: User
163
# name: admin@example.com
164
# - kind: ServiceAccount
165
# namespace: kube-system
166
# name: default
167
# matchConditions:
168
# - name: exclude-custom
169
# expression: "!object.metadata.name.startsWith('temp-')"
170
171
# -- Add preconditions to individual policies.
172
# Policies with multiple rules can have individual rules excluded by using the name of the rule as the key in the `policyPreconditions` map.
173
policyPreconditions: {}
174
# # Exclude resources from individual policies
175
# require-run-as-non-root-user:
176
# all:
177
# - key: "{{ request.object.metadata.name }}"
178
# operator: NotEquals
179
# value: "dcgm-exporter*"
180
# # Policies with multiple rules can have individual rules excluded
181
# require-drop-all:
182
# any:
183
# - key: "{{ request.object.metadata.name }}"
184
# operator: NotEquals
185
# value: "dcgm-exporter*"
186
# adding-capabilities-strict:
187
# all:
188
# - key: "{{ request.object.metadata.name }}"
189
# operator: NotEquals
190
# value: "dcgm-exporter*"
191
192
# -- Customize the target Pod controllers for the auto-generated rules. (Eg. `none`, `Deployment`, `DaemonSet,Deployment,StatefulSet`)
193
# For more info https://kyverno.io/docs/policy-types/cluster-policy/autogen/.
194
autogenControllers: ""
195
196
# -- Name override.
197
nameOverride:
198
199
# -- Additional Annotations.
200
customAnnotations: {}
201
202
# -- Define custom annotations for specific policies.
203
# Per-policy entries override defaults when they share the same key.
204
customAnnotationsByPolicy: {}
205
# disallow-host-path:
206
# my-custom-annotation: "some-value"
207
208
# -- Additional labels.
209
customLabels: {}
210
211
# -- Policies background mode
212
background: true
213
214
# -- (bool) SkipBackgroundRequests bypasses admission requests that are sent by the background controller
215
skipBackgroundRequests: ~
216
217
# -- Kyverno version
218
# The default of "autodetect" will try to determine the currently installed version from the deployment
219
kyvernoVersion: autodetect
220
221
# -- Kubernetes version override
222
# Override default value of kubeVersion set by release team taken from Chart.yaml with custom value. Ideally range of versions no more than two prior (ex., 1.28-1.31), must be enclosed in quotes.
223
kubeVersionOverride:
224

The trusted source for open source

Talk to an expert
PrivacyTerms

Product

Chainguard ContainersChainguard LibrariesChainguard VMsChainguard OS PackagesChainguard ActionsChainguard Agent SkillsIntegrationsPricing
© 2026 Chainguard, Inc. All Rights Reserved.
Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.