Apply Pod Security Standards at the Namespace Level
Kubernetes Docs · نسخهٔ f284a9e7c87f · CC BY 4.0 برای مستندات و مجوزهای همراه
{{% alert title="Note" %}} This tutorial applies only for new clusters. {{% /alert %}}
Pod Security Admission is an admission controller that applies Pod Security Standards when pods are created. It is a feature GA'ed in v1.25. In this tutorial, you will enforce the baseline Pod Security Standard, one namespace at a time.
You can also apply Pod Security Standards to multiple namespaces at once at the cluster level. For instructions, refer to Apply Pod Security Standards at the cluster level.
{{% heading "prerequisites" %}}
Install the following on your workstation:
- kind
- kubectl
Create cluster
- Create a
kindcluster as follows:
kind create cluster --name psa-ns-levelThe output is similar to this:
Creating cluster "psa-ns-level" ...
✓ Ensuring node image (kindest/node:v{{< skew currentPatchVersion >}}) 🖼
✓ Preparing nodes 📦
✓ Writing configuration 📜
✓ Starting control-plane 🕹️
✓ Installing CNI 🔌
✓ Installing StorageClass 💾
Set kubectl context to "kind-psa-ns-level"
You can now use your cluster with:
kubectl cluster-info --context kind-psa-ns-level
Not sure what to do next? 😅 Check out https://kind.sigs.k8s.io/docs/user/quick-start/- Set the kubectl context to the new cluster:
kubectl cluster-info --context kind-psa-ns-levelThe output is similar to this:
Kubernetes control plane is running at https://127.0.0.1:50996
CoreDNS is running at https://127.0.0.1:50996/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.Create a namespace
Create a new namespace called example:
kubectl create ns exampleThe output is similar to this:
namespace/example createdEnable Pod Security Standards checking for that namespace
- Enable Pod Security Standards on this namespace using labels supported by
built-in Pod Security Admission. In this step you will configure a check to warn on Pods that don't meet the latest version of the _baseline_ pod security standard.
kubectl label --overwrite ns example \
pod-security.kubernetes.io/warn=baseline \
pod-security.kubernetes.io/warn-version=latest- You can configure multiple pod security standard checks on any namespace, using labels.
The following command will enforce the baseline Pod Security Standard, but warn and audit for restricted Pod Security Standards as per the latest version (default value)
kubectl label --overwrite ns example \
pod-security.kubernetes.io/enforce=baseline \
pod-security.kubernetes.io/enforce-version=latest \
pod-security.kubernetes.io/warn=restricted \
pod-security.kubernetes.io/warn-version=latest \
pod-security.kubernetes.io/audit=restricted \
pod-security.kubernetes.io/audit-version=latestVerify the Pod Security Standard enforcement
- Create a baseline Pod in the
examplenamespace:
kubectl apply -n example -f https://k8s.io/examples/security/example-baseline-pod.yamlThe Pod does start OK; the output includes a warning. For example:
Warning: would violate PodSecurity "restricted:latest": allowPrivilegeEscalation != false (container "nginx" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "nginx" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or container "nginx" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container "nginx" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")
pod/nginx created- Create a baseline Pod in the
defaultnamespace:
kubectl apply -n default -f https://k8s.io/examples/security/example-baseline-pod.yamlOutput is similar to this:
pod/nginx createdThe Pod Security Standards enforcement and warning settings were applied only to the example namespace. You could create the same Pod in the default namespace with no warnings.
Clean up
Now delete the cluster which you created above by running the following command:
kind delete cluster --name psa-ns-level{{% heading "whatsnext" %}}
- Run a
shell script to perform all the preceding steps all at once.
- Create kind cluster
- Create new namespace
- Apply
baselinePod Security Standard inenforcemode while applying
restricted Pod Security Standard also in warn and audit mode.
- Create a new pod with the following pod security standards applied
- Pod Security Admission
- Pod Security Standards
- Apply Pod Security Standards at the cluster level