6792fba91f
* rename root fs check * speed up docker build * refactor webhook to be more generic * delete controllers pkg * revert deploy * fix example config * remove controllersToScan config * fix lint error * fix webhook name * FileSystem -> Filesystem * update deps * skip node owners * clean up meta tracking Co-authored-by: Robert Brennan <bobby.brennan@gmail.com>
1.8 KiB
Security
Polaris supports a number of checks related to security.
| key | default | description |
|---|---|---|
security.hostIPCSet |
error |
Fails when hostIPC attribute is configured. |
security.hostPIDSet |
error |
Fails when hostPID attribute is configured. |
security.notReadOnlyRootFilesystem |
warning |
Fails when securityContext.readOnlyRootFilesystem is not true. |
security.privilegeEscalationAllowed |
error |
Fails when securityContext.allowPrivilegeEscalation is true. |
security.runAsRootAllowed |
error |
Fails when securityContext.runAsNonRoot is not true. |
security.runAsPrivileged |
error |
Fails when securityContext.privileged is true. |
Security Capabilities
Additional validations are available to ensure pods are running with a limited set of capabilities. More information is available in our Security Capabilities documentation.
Background
Securing workloads in Kubernetes is an important part of overall cluster security. The overall goal should be to ensure that containers are running with as minimal privileges as possible. This includes avoiding privilege escalation, not running containers with a root user, and using read only file systems wherever possible.
Much of this configuration can be found in the securityContext attribute for both Kubernetes pods and containers. Where configuration is available at both a pod and container level, Polaris validates both.