liveBook · Manning

Baseline policy

As explained in Kubernetes for Developers

The Baseline Pod Security profile prevents Pods from elevating privileges to obtain administrative access while preserving broader compatibility.

The Baseline profile prevents Pods from elevating privileges to gain administrative access while preserving compatibility with typical applications. It provides a practical default for nonadministrative workloads. section 12.5.1 section 12.5.2

Apply the profile according to the workload’s operational role:

  • Use Baseline for ordinary application workloads to reduce the impact of a compromised container without commonly breaking application compatibility. section 12.5.2
  • Reserve the Privileged profile for administrative or system workloads that genuinely require unrestricted administrative access. section 12.5.1
  • Place administrative workloads in separate namespaces from common application workloads. section 12.5.2

Choosing between Baseline and Restricted

Restricted adds defense-in-depth requirements, including running containers as non-root, and can require security-context changes. Baseline offers a broader compatibility margin when those requirements are impractical. section 12.5.1 section 12.5.2

How Kubernetes for Developers covers it

How deep it goes
Defines Baseline and contrasts it with other profiles, but does not provide a Baseline-specific namespace configuration.
Examples
Contrasts ordinary workloads with administrative workloads and contrasts Baseline compatibility with Restricted hardening requirements.
What you can do after
Apply Baseline to nonadministrative workloads and isolate Privileged administrative workloads in separate namespaces.
How it connects
Connects Baseline with Pod Security admission, namespaces, Privileged, Restricted, and Pod security context.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Kubernetes for Developers. The section links point to the parts of the book it draws on.