Add Kyverno admission policies and CIS mappings
Kube-bench CIS scan / Scan ephemeral K3s cluster (push) Failing after 3m11s
Kube-bench CIS scan / Scan ephemeral K3s cluster (push) Failing after 3m11s
This commit is contained in:
@@ -0,0 +1,49 @@
|
||||
apiVersion: kyverno.io/v1
|
||||
kind: ClusterPolicy
|
||||
metadata:
|
||||
name: require-resource-limits
|
||||
annotations:
|
||||
policies.kyverno.io/title: Require CPU and memory limits
|
||||
policies.kyverno.io/category: Resource governance
|
||||
policies.kyverno.io/severity: medium
|
||||
# Supplemental hardening aligned with CIS 5.7.3 workload controls. The
|
||||
# CIS benchmark does not define a one-to-one resource-limit test.
|
||||
policies.kyverno.io/cis-control: "5.7.3 supplemental"
|
||||
spec:
|
||||
validationFailureAction: Enforce
|
||||
background: false
|
||||
failurePolicy: Fail
|
||||
rules:
|
||||
- name: containers-have-resource-limits
|
||||
match:
|
||||
any:
|
||||
- resources:
|
||||
kinds:
|
||||
- Pod
|
||||
namespaceSelector:
|
||||
matchLabels:
|
||||
security-baseline/open: "true"
|
||||
validate:
|
||||
message: Every container must define CPU and memory limits.
|
||||
foreach:
|
||||
- list: request.object.spec.containers[]
|
||||
deny:
|
||||
conditions:
|
||||
any:
|
||||
- key: "{{ element.resources.limits.cpu || '' }}"
|
||||
operator: Equals
|
||||
value: ""
|
||||
- key: "{{ element.resources.limits.memory || '' }}"
|
||||
operator: Equals
|
||||
value: ""
|
||||
- list: request.object.spec.initContainers[]
|
||||
deny:
|
||||
conditions:
|
||||
any:
|
||||
- key: "{{ element.resources.limits.cpu || '' }}"
|
||||
operator: Equals
|
||||
value: ""
|
||||
- key: "{{ element.resources.limits.memory || '' }}"
|
||||
operator: Equals
|
||||
value: ""
|
||||
|
||||
Reference in New Issue
Block a user