Why Pod security standards in Kubernetes? - Purpose & Use Cases

The Big Idea

What if a simple set of rules could stop security risks before they even start in your Kubernetes pods?

The Scenario

Imagine you manage a busy apartment building where every tenant can bring in any kind of furniture or appliances without rules.

Some tenants bring dangerous or noisy items that disturb others or cause damage.

Without clear rules, chaos and risks grow quickly.

The Problem

Manually checking each tenant's items is slow and tiring.

You might miss dangerous things or forget to enforce rules consistently.

This leads to security risks, unhappy tenants, and more work fixing problems later.

The Solution

Pod security standards act like clear building rules for Kubernetes pods.

They automatically check and enforce safe settings for pods before they run.

This keeps the environment secure, consistent, and easier to manage.

Before vs After

✗ Before

kubectl apply -f pod.yaml  # hoping pod is secure

✓ After

kubectl label ns default pod-security.kubernetes.io/enforce=restricted && kubectl apply -f pod.yaml  # Enforces restricted PSS

What It Enables

It enables safe, automated control over what pods can do, protecting your system without extra manual work.

Real Life Example

A company uses pod security standards to block pods that try to run as root or access host files, preventing accidental or malicious damage.

Key Takeaways

Manual security checks are slow and error-prone.

Pod security standards automate and enforce safe pod configurations.

This leads to safer, more reliable Kubernetes environments.

Practice

1. What is the main purpose of Kubernetes Pod Security Standards?

easy

A. To control pod permissions and prevent risky behaviors

B. To increase pod resource limits automatically

C. To schedule pods on specific nodes

D. To monitor pod network traffic

Solution

1. Step 1: Understand Pod Security Standards

   Pod Security Standards define rules to restrict pod permissions and behaviors.

2. Step 2: Identify the main goal

   The goal is to prevent risky pod behaviors like running as root or privileged mode.

3. Final Answer:

   To control pod permissions and prevent risky behaviors -> Option A

4. Quick Check:

   Pod Security Standards = Control permissions [OK]

Hint: Pod Security Standards limit pod permissions to keep cluster safe [OK]

Common Mistakes:

• Confusing security standards with resource management
• Thinking it schedules pods on nodes
• Assuming it monitors network traffic

2. Which of the following is the correct way to label a namespace to enforce the 'restricted' Pod Security Standard in Kubernetes?

easy

A. kubectl set security namespace myns restricted

B. kubectl label pod mypod pod-security.kubernetes.io/enforce=restricted

C. kubectl annotate namespace myns pod-security.kubernetes.io/enforce=restricted

D. kubectl label namespace myns pod-security.kubernetes.io/enforce=restricted

Solution

1. Step 1: Identify correct resource and command

   Pod Security Standards are enforced by labeling namespaces, not pods.

2. Step 2: Check correct syntax for labeling namespace

   The correct command is 'kubectl label namespace <name> pod-security.kubernetes.io/enforce=restricted'.

3. Final Answer:

   kubectl label namespace myns pod-security.kubernetes.io/enforce=restricted -> Option D

4. Quick Check:

   Label namespace with enforce=restricted [OK]

Hint: Label namespaces, not pods, to enforce Pod Security Standards [OK]

Common Mistakes:

• Labeling pods instead of namespaces
• Using annotate instead of label
• Using invalid kubectl commands

3. Given this pod spec snippet, which Pod Security Standard will it most likely violate?

{
  "securityContext": {
    "runAsUser": 0,
    "privileged": true
  }
}

medium

A. Baseline

B. Restricted

C. Privileged

D. None

Solution

1. Step 1: Analyze pod securityContext

   The pod runs as user 0 (root) and uses privileged mode, which is risky.

2. Step 2: Match with Pod Security Standards

   Restricted standard forbids running as root and privileged mode, so this pod violates Restricted.

3. Final Answer:

   Restricted -> Option B

4. Quick Check:

   Root + privileged = violates Restricted [OK]

Hint: Root user and privileged mode break Restricted standard [OK]

Common Mistakes:

• Confusing Baseline and Restricted standards
• Thinking privileged mode is allowed in Restricted
• Assuming no violation if pod runs as root

4. You labeled a namespace with pod-security.kubernetes.io/enforce=restricted, but pods running as root are still allowed. What is the most likely reason?

medium

A. The Pod Security Admission controller is not enabled in the cluster

B. The label was applied to the pod instead of the namespace

C. The pod spec is missing the securityContext field

D. The namespace label should be 'pod-security.kubernetes.io/warn=restricted'

Solution

1. Step 1: Understand enforcement mechanism

   Pod Security Standards enforcement requires the Pod Security Admission controller enabled in the cluster.

2. Step 2: Check other options

   Labeling pod instead of namespace or missing securityContext won't bypass enforcement if controller is active. Warning label only warns, does not enforce.

3. Final Answer:

   The Pod Security Admission controller is not enabled in the cluster -> Option A

4. Quick Check:

   Admission controller must be enabled for enforcement [OK]

Hint: Enforcement needs admission controller enabled [OK]

Common Mistakes:

• Applying label to pod instead of namespace
• Confusing warn label with enforce label
• Assuming missing securityContext disables enforcement

5. You want to enforce the 'baseline' Pod Security Standard but allow some pods to run as root for legacy reasons. Which approach best balances security and flexibility?

hard

A. Disable Pod Security Admission controller and manually review pods

B. Label the namespace with 'pod-security.kubernetes.io/enforce=restricted' and remove root user from all pods

C. Label the namespace with 'pod-security.kubernetes.io/enforce=baseline' and use Pod Security Exceptions for specific pods

D. Label each pod with 'pod-security.kubernetes.io/enforce=baseline' individually

Solution

1. Step 1: Understand baseline enforcement with exceptions

   Baseline standard is less strict than restricted and allows some flexibility.

2. Step 2: Use exceptions for legacy pods

   Pod Security Exceptions allow specific pods to bypass some rules while enforcing baseline on the namespace.

3. Step 3: Evaluate other options

   Restricted is stricter, disabling admission controller removes security, labeling pods individually is not standard practice.

4. Final Answer:

   Label the namespace with 'pod-security.kubernetes.io/enforce=baseline' and use Pod Security Exceptions for specific pods -> Option C

5. Quick Check:

   Baseline + exceptions = balance security and legacy needs [OK]

Hint: Use baseline label plus exceptions for legacy pods [OK]

Common Mistakes:

• Using restricted standard which is too strict
• Disabling admission controller reduces security
• Labeling pods individually instead of namespace