Pod security admission controller in Kubernetes - Time & Space Complexity

Time Complexity: Pod security admission controller

O(n)

Understanding Time Complexity

We want to understand how the Pod Security Admission Controller's processing time changes as more pods are created or updated in a Kubernetes cluster.

Specifically, how does the controller's work grow when handling many pod requests?

Scenario Under Consideration

Analyze the time complexity of the following admission controller snippet.

apiVersion: admissionregistration.k8s.io/v1
kind: ValidatingAdmissionWebhook
metadata:
  name: pod-security-webhook
webhooks:
- name: pod-security.kubernetes.io
  rules:
  - operations: ["CREATE", "UPDATE"]
    apiGroups: [""]
    apiVersions: ["v1"]
    resources: ["pods"]
  admissionReviewVersions: ["v1"]
  sideEffects: None

This webhook intercepts pod creation and update requests to check if they meet security standards before allowing them.

Identify Repeating Operations

• Primary operation: The admission controller inspects each pod's security settings one by one as requests come in.
• How many times: Once per pod creation or update request.

How Execution Grows With Input

Each pod request is checked individually, so the total work grows directly with the number of pod requests.

Input Size (n)	Approx. Operations
10	10 checks
100	100 checks
1000	1000 checks

Pattern observation: The work grows in a straight line as more pods are processed.

Final Time Complexity

Time Complexity: O(n)

This means the time to check pods grows directly in proportion to how many pods are created or updated.

Common Mistake

[X] Wrong: "The admission controller checks all pods in the cluster every time a new pod is created."

[OK] Correct: The controller only checks the pod in the current request, not all existing pods, so it does not do extra work for past pods.

Interview Connect

Understanding how admission controllers scale helps you design systems that stay fast as clusters grow. This skill shows you can think about real-world system behavior clearly.

Self-Check

What if the admission controller also checked all existing pods in the cluster on each new pod request? How would the time complexity change?

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