The module has 4 alerts.
The module is enabled by default in the following bundles: Default
, Managed
.
The module is disabled by default in the Minimal
bundle.
The module is configured using the ModuleConfig custom resource named admission-policy-engine
(learn more about setting up Deckhouse…).
Example of the ModuleConfig/admission-policy-engine
resource for configuring the module:
apiVersion: deckhouse.io/v1alpha1
kind: ModuleConfig
metadata:
name: admission-policy-engine
spec:
version: 1
enabled: true
settings: # <-- Module parameters from the "Parameters" section below.
Parameters
Schema version: 1
- settings
- settings.denyVulnerableImages
Trivy provider will deny creation of the
Pod
/Deployment
/StatefulSet
/DaemonSet
with vulnerable images in namespaces withsecurity.deckhouse.io/trivy-provider: ""
label.This feature is available in enterprise edition only.
- settings.denyVulnerableImages.enabled
Enable trivy provider.
Default:
false
- settings.denyVulnerableImages.registrySecrets
List of additional registry secrets to use for downloading images from private registries.
By default, the
deckhouse-registry
secret is used to download images for scanning.Default:
[]
- settings.denyVulnerableImages.registrySecrets.name
Required value
- settings.denyVulnerableImages.registrySecrets.namespace
Required value
- settings.denyVulnerableImages.storageClass
The name of the StorageClass to use for
trivy-provider
.false
— forces theemptyDir
usage. Manually delete the old PVC and restart Pod, after setting the parameter.Examples:
storageClass: ceph-ssd
storageClass: 'false'
- settings.podSecurityStandards
Pod Security Standards policy settings (PSS).
- settings.podSecurityStandards.defaultPolicy
Sets the default Pod Security Standards policy for all non-system namespaces:
Privileged
— an unrestricted policy. Privilege escalation is possible with this policy;Baseline
— a policy with minimum restrictions that prevents privilege escalation;Restricted
— a policy with maximum restrictions that conforms to current best practices for securely running applications in a cluster.
By default:
Baseline
— if a Deckhouse version starting with v1.55 is being installed;Privileged
— if a Deckhouse version lower than v1.55 is being installed (upgrading Deckhouse in a cluster to v1.55+ does not automatically result in a default policy change).
Allowed values:
Privileged
,Baseline
,Restricted
- settings.podSecurityStandards.enforcementAction
The enforcement action to control what to do with the result of the constraint.
- Deny — Deny action.
- Dryrun — No action. It is used when debugging. Information about the event can be viewed in Grafana or in the console via kubectl.
- Warn — Same as
Dryrun
. In addition to the event information, it provides some info on why that constraint would have been denied if you had setDeny
instead ofWarn
.
Default:
"Deny"
Allowed values:
Warn
,Deny
,Dryrun
- settings.podSecurityStandards.policies
Sets additional policy parameters.
- settings.podSecurityStandards.policies.hostPorts
HostPort constraint settings.
- settings.podSecurityStandards.policies.hostPorts.knownRanges
Set the range of known ports which will be allowed in a hostPort binding.
- settings.podSecurityStandards.policies.hostPorts.knownRanges.max
- settings.podSecurityStandards.policies.hostPorts.knownRanges.min