mirror of
https://github.com/kyverno/kyverno.git
synced 2024-12-14 11:57:48 +00:00
update markdown
This commit is contained in:
parent
4fbc57bfed
commit
764c353fdd
1 changed files with 12 additions and 5 deletions
|
@ -15,6 +15,13 @@ apiVersion: kyverno.io/v1alpha1
|
|||
kind: ClusterPolicy
|
||||
metadata:
|
||||
name: validate-new-capabilities
|
||||
annotations:
|
||||
policies.kyverno.io/category: Security Context
|
||||
policies.kyverno.io/description: Linux allows defining fine-grained permissions using
|
||||
capabilities. With Kubernetes, it is possible to add capabilities that escalate the
|
||||
level of kernel access and allow other potentially dangerous behaviors. This policy
|
||||
enforces that pods cannot add new capabilities. Other policies can be used to set
|
||||
default capabilities.
|
||||
spec:
|
||||
rules:
|
||||
- name: deny-new-capabilities
|
||||
|
@ -26,13 +33,13 @@ spec:
|
|||
message: "Capabilities cannot be added"
|
||||
anyPattern:
|
||||
- spec:
|
||||
securityContext:
|
||||
capabilities:
|
||||
X(add): null
|
||||
=(securityContext):
|
||||
=(capabilities):
|
||||
X(add): null
|
||||
- spec:
|
||||
containers:
|
||||
- name: "*"
|
||||
securityContext:
|
||||
(capabilities):
|
||||
=(securityContext):
|
||||
=(capabilities):
|
||||
X(add): null
|
||||
````
|
||||
|
|
Loading…
Reference in a new issue