liveBook · Manning

Kubernetes manifest

As explained in Software Security for Developers

A Kubernetes manifest is a declarative configuration document that specifies Kubernetes resources and their desired state.

A Kubernetes manifest is a YAML configuration document that declares application resources and their desired operating configuration. It can configure nearly every aspect of how an application runs, so insecure settings can undermine an otherwise secure container or cluster. section 3.2

Secure deployment work divides responsibilities:

  • Developers write deployment manifests that follow Kubernetes security best practices and package applications securely. section 3.2 section 3.4
  • Platform engineering teams provide and secure the Kubernetes cluster; cluster deployment and management remain a separate responsibility. section 3.2

Practical security check

Before deploying an application, review its YAML deployment manifest alongside its container image: both must follow security best practices for secure Kubernetes operation. section 3.2

How Software Security for Developers covers it

How deep it goes
Explains YAML manifests and responsibilities, but defers detailed secure-manifest practices to later treatment.
Examples
Uses YAML deployment manifests as the concrete configuration artifact for running applications on Kubernetes.
What it assumes
Assumes basic Kubernetes knowledge and distinguishes application deployment configuration from securing and managing the cluster.
What you can do after
Apply it by writing deployment manifests that configure applications according to Kubernetes security best practices.
How it connects
Connects secure container images, Kubernetes clusters, platform engineering, and deployment security best practices.

Also explained in

Compare how 10 books explain Kubernetes manifest →

Related concepts

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