Pod security admission controller in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Pod Security Admission Controller Modes

Which mode of the Pod Security Admission Controller enforces policies and blocks pods that do not comply?

A Warn mode

B Monitor mode

C Enforce mode

D Audit mode

💡 Hint

Think about which mode actively stops non-compliant pods from running.

Enforce mode blocks pods that violate the security policies, preventing them from being created or updated.

💻 Command Output

intermediate

Pod Security Admission Controller Policy Enforcement Output

What is the output when a pod violates the 'restricted' Pod Security Admission policy in enforce mode?

Kubernetes

kubectl apply -f pod.yaml

A Error from server (Forbidden): error when creating "pod.yaml": admission webhook "podsecurity.k8s.io" denied the request: restricted: forbidden fields present

B Warning: pod "mypod" violates policy but created

C pod "mypod" created with warnings

D pod "mypod" created

💡 Hint

Enforce mode blocks pods and returns an error message.

In enforce mode, the admission controller denies pod creation and returns a forbidden error with details about the violation.

❓ Configuration

advanced

Configuring Pod Security Admission Controller for a Namespace

Which YAML snippet correctly configures the Pod Security Admission Controller to enforce the 'baseline' policy on the namespace 'dev-team'?

A

apiVersion: v1
kind: Namespace
metadata:
  name: dev-team
  annotations:
    pod-security.kubernetes.io/warn: baseline

B

apiVersion: v1
kind: Namespace
metadata:
  name: dev-team
  annotations:
    pod-security.kubernetes.io/enforce: baseline

C

apiVersion: v1
kind: Namespace
metadata:
  name: dev-team
  annotations:
    pod-security.kubernetes.io/enforce: restricted

D

apiVersion: v1
kind: Namespace
metadata:
  name: dev-team
  annotations:
    pod-security.kubernetes.io/audit: baseline

💡 Hint

Enforce annotation applies the policy strictly.

The 'pod-security.kubernetes.io/enforce' annotation with value 'baseline' applies the baseline policy in enforce mode to the namespace.

❓ Troubleshoot

advanced

Diagnosing Pod Creation Failure with Pod Security Admission Controller

A developer reports that their pod creation fails with the message: admission webhook "podsecurity.k8s.io" denied the request: restricted: forbidden fields present. What is the most likely cause?

A The pod spec includes fields disallowed by the 'restricted' Pod Security policy enforced on the namespace.

B The Kubernetes API server is down and cannot process the request.

C The pod YAML file is missing required fields like 'metadata' or 'spec'.

D The user does not have permission to create pods in the cluster.

💡 Hint

Focus on the 'forbidden fields present' part of the error message.

The error indicates the pod spec violates the enforced 'restricted' policy by including disallowed fields such as privileged containers or host networking.

🔀 Workflow

expert

Pod Security Admission Controller Policy Upgrade Workflow

You want to upgrade a namespace from 'baseline' to 'restricted' Pod Security policy without breaking existing workloads. Which sequence of steps is best?

A 2,1,3,4

B 3,1,2,4

C 1,3,2,4

D 1,2,3,4

💡 Hint

Think about a safe upgrade path that warns first before enforcing.

First warn to detect violations, fix them, then enforce the policy, and finally clean up the warn annotation.

Practice

1. What is the primary purpose of the Pod Security Admission Controller in Kubernetes?

easy

A. To monitor pod resource usage

B. To manage network traffic between pods

C. To schedule pods on specific nodes

D. To enforce security policies on pods based on predefined security levels

Solution

1. Step 1: Understand the role of Pod Security Admission Controller

   This controller enforces security policies on pods to ensure they meet security standards.

2. Step 2: Differentiate from other controllers

   It does not manage networking, scheduling, or resource monitoring, which are handled by other components.

3. Final Answer:

   To enforce security policies on pods based on predefined security levels -> Option D

4. Quick Check:

   Pod Security Admission = Enforce security policies [OK]

Hint: Remember: Pod Security Admission controls pod security levels [OK]

Common Mistakes:

• Confusing it with network or scheduling controllers
• Thinking it monitors resource usage
• Assuming it manages pod lifecycle

2. Which of the following is the correct way to specify the enforce mode for the Pod Security Admission Controller in a Kubernetes API server configuration?

easy

A. --enable-admission-plugins=PodSecurity --pod-security-enforce=audit

B. --enable-admission-plugins=PodSecurity --pod-security-mode=enforce

C. --enable-admission-plugins=PodSecurity --pod-security-enforce=restricted

D. --admission-control=PodSecurity --pod-security-enforce=baseline

Solution

1. Step 1: Identify correct flag names for Pod Security Admission

   The correct flags are --enable-admission-plugins=PodSecurity and --pod-security-enforce=LEVEL where LEVEL is one of privileged, baseline, or restricted.

2. Step 2: Verify option syntax and values

   --enable-admission-plugins=PodSecurity --pod-security-enforce=restricted: --enable-admission-plugins=PodSecurity --pod-security-enforce=restricted uses correct flag names and a valid security level 'restricted'. Options A uses invalid level, B uses incorrect flag --pod-security-mode, and C uses deprecated --admission-control.

3. Final Answer:

   --enable-admission-plugins=PodSecurity --pod-security-enforce=restricted -> Option C

4. Quick Check:

   Correct flags + valid level = --enable-admission-plugins=PodSecurity --pod-security-enforce=restricted [OK]

Hint: Look for exact flag names and valid security levels [OK]

Common Mistakes:

• Using wrong flag names like --admission-control
• Confusing enforce mode with audit or warn
• Using invalid security levels

3. Given this Pod Security Admission configuration snippet:

apiVersion: policy/v1
kind: PodSecurity
metadata:
  name: enforce-baseline
spec:
  enforce:
    level: baseline
    version: "latest"
  warn:
    level: restricted
    version: "latest"
  audit:
    level: privileged
    version: "latest"

What will happen if a pod with privileged permissions is created?

medium

A. The pod creation will be blocked due to enforcement at baseline level

B. The pod creation will succeed but a warning will be logged

C. The pod creation will succeed without any warnings or audits

D. The pod creation will be audited but allowed

Solution

1. Step 1: Understand enforcement level

   The enforce level is set to baseline, which blocks pods that do not meet baseline security standards, including privileged pods.

2. Step 2: Analyze pod permissions against levels

   Privileged pods exceed baseline restrictions, so enforcement blocks creation. Warnings and audits apply to lower levels but enforcement is strictest.

3. Final Answer:

   The pod creation will be blocked due to enforcement at baseline level -> Option A

4. Quick Check:

   Enforce baseline blocks privileged pods [OK]

Hint: Enforce blocks pods below level; privileged > baseline [OK]

Common Mistakes:

• Confusing warn or audit with enforce
• Assuming privileged pods pass baseline enforcement
• Ignoring enforcement priority over warnings

4. You configured the Pod Security Admission Controller with --pod-security-enforce=restricted, but pods with privileged containers are still being created. What is the most likely cause?

medium

A. The pods are created in namespaces labeled to exempt enforcement

B. The admission controller is not enabled in the API server

C. The pod spec has incorrect securityContext fields

D. The Kubernetes version does not support Pod Security Admission Controller

Solution

1. Step 1: Check admission controller enablement

   If the controller was not enabled, no enforcement would occur cluster-wide, but the question implies partial enforcement.

2. Step 2: Understand namespace labels impact

   Namespaces can be labeled to exempt or relax enforcement, allowing privileged pods despite cluster-wide settings.

3. Step 3: Consider other options

   Incorrect pod specs or Kubernetes version issues would cause errors or no enforcement at all, not selective allowance.

4. Final Answer:

   The pods are created in namespaces labeled to exempt enforcement -> Option A

5. Quick Check:

   Namespace labels can exempt enforcement [OK]

Hint: Check namespace labels for enforcement exemptions [OK]

Common Mistakes:

• Assuming controller is disabled without checking labels
• Ignoring namespace-level exemptions
• Blaming pod spec errors for enforcement bypass

5. You want to enforce the Pod Security Admission Controller to block all pods that request hostPath volumes except in a specific namespace called trusted. How should you configure this?

hard

A. Set cluster-wide enforcement to restricted and label the trusted namespace with pod-security.kubernetes.io/enforce: baseline

B. Set cluster-wide enforcement to restricted and label the trusted namespace with pod-security.kubernetes.io/enforce: privileged

C. Set cluster-wide enforcement to baseline and label the trusted namespace with pod-security.kubernetes.io/enforce: baseline

D. Set cluster-wide enforcement to privileged and label the trusted namespace with pod-security.kubernetes.io/enforce: restricted

Solution

1. Step 1: Understand security levels and hostPath restrictions

   The restricted level blocks hostPath volumes, while privileged allows them.

2. Step 2: Apply cluster-wide enforcement and namespace override

   Set cluster-wide enforcement to restricted to block hostPath everywhere by default. Label the trusted namespace with pod-security.kubernetes.io/enforce: privileged to allow exceptions.

3. Step 3: Verify option correctness

   Set cluster-wide enforcement to restricted and label the trusted namespace with pod-security.kubernetes.io/enforce: privileged correctly sets cluster-wide to restricted and trusted namespace to privileged, allowing hostPath only there.

4. Final Answer:

   Set cluster-wide enforcement to restricted and label the trusted namespace with pod-security.kubernetes.io/enforce: privileged -> Option B

5. Quick Check:

   Cluster restricted + trusted privileged = hostPath allowed only in trusted [OK]

Hint: Cluster restrict + namespace privileged allows exceptions [OK]

Common Mistakes:

• Setting cluster enforcement too low to block hostPath
• Using baseline instead of privileged for exceptions
• Labeling trusted namespace with a stricter level