liveBook · Manning

Kubernetes Secret

As explained in Google Anthos in Action

A Kubernetes Secret is a resource for storing data intended to be confidential or sensitive for use by workloads.

A Kubernetes Secret stores external information intended for use by Pods when that information is sensitive. Unlike ConfigMaps, Secret values use Base64 encoding, which supports binary data but does not provide meaningful confidentiality: anyone able to view a Secret can trivially decode it. section 3.2.6

Treat Secret protection as a layered operational concern:

  • Use an external secret manager such as Vault or Google Secret Manager when stronger protection is required. section 3.2.6
  • Enable encryption for Secrets stored in etcd, while recognizing that this protects the database value rather than the Secret throughout Kubernetes. section 3.2.6
  • Combine external protection with etcd encryption to cover both cluster handling and database storage. section 3.2.6

How Google Anthos in Action covers it

How deep it goes
Explains representation and storage risks, but stops short of defining Secret manifests or consumption commands.
Examples
Uses Pod-consumed external data, Vault, Google Secret Manager, and etcd encryption as operational examples.
What you can do after
Operate/configure Secret protection by distinguishing Base64 encoding from encryption and layering external and etcd safeguards.
How it connects
Connects Secrets with ConfigMaps, Pods, etcd, Base64 encoding, and external secret managers.

Also explained in

Compare how 6 books explain Kubernetes Secret →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.