Home/By platform/Everything for Kubernetes
Everything for Kubernetes
Every template, lesson, refresher, and planner on this site that applies to Kubernetes, in one place.
This page lists what runs inside a cluster, and the templates each cloud needs for its managed Kubernetes service.
Alerts
The templates below create 147 alerts for Kubernetes. Each link opens the alerts table filtered to one platform, with what fires each alert, the log it reads, and how someone hears.
Templates
Seven templates have code for Kubernetes, written for Argo CD and Terraform. All 39 levels are Ready. What each level includes.
Incident response
The lessons to read before an incident on Kubernetes, the most specific first, and to keep open during one.
Container escape, token theft, workload identity abuse, admission bypass, and keeping a pod for investigation.
Where container evidence lives, the order to capture it, checkpointing, and moves that destroy it.
Runbooks for checkpointing a container and capturing a node's memory on EKS and GKE, and reading both.
Audit logs, pod identities, nodes, and managed modes on GKE and EKS, and how to respond on each.
Audit logs, pod and node identities, disks, and managed modes on AKS and OKE, and how to respond on each.
Credentials Kubernetes cannot revoke, where attackers persist, rotating the cluster CA on four clouds, and replacing nodes.
One-page refreshers
Each prints on one page. Every template in the table above links its own.
The common paths through a cluster, where each one leaves traces, and what stops it.
Where a container keeps its evidence, when each part disappears, and the order to capture it in.
Which nodes let you checkpoint a container or capture their memory, and the commands for each on EKS and GKE.
What each cloud records about a cluster, how to keep a node, and what to rely on when you cannot reach it.
What each service records about a cluster, what a pod can reach on its node, and how to keep the node's disks.
What outlives a deleted pod, where attackers persist in Kubernetes, and how to rotate what cannot be revoked.
A controller inside a Kubernetes cluster that keeps the cluster matching a Git repository, and puts back changes made by hand.
Log planning
The log source planner lists every log source to turn on, how long each is kept by default, and what it costs. This link opens it set to EKS, AKS, GKE, and OKE.