How to make Kubernetes rhyme with prod readiness
summary
Defines a practical production checklist that closes the gap between a Kubernetes cluster and a production cluster by naming concrete gaps and tools: add centralized logging and metrics via Prometheus and Grafana, use an Ingress controller or Gateway API plus Calico/Cilium for NetworkPolicy enforcement, provide PV backing and backups with Velero, templatize manifests with Helm, Kustomize or Carvel and deploy with Argo CD or Flux, consider Cluster API or Terraform for infra, and prefer managed offerings unless compliance or scale force on‑prem.
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker background
- 1:46What is production readiness
- 3:31Kubernetes basics and features
- 7:02Missing pieces in vanilla Kubernetes
- 9:04Networking challenges and solutions
- 11:53Observability in Kubernetes
- 13:58Security considerations for clusters
- 16:27Workload stability and automation
- 18:59Tooling checklist for production
- 20:03Infrastructure and networking tools
- 21:27Observability and security tools
- 22:30Workload management and build packs
- 23:15Managed vs self-hosted Kubernetes
- 25:22Cloud vs on-prem decisions
- 26:47Summary and closing remarks
related talks
32mHow to make kubernetes rhyme with prod readiness
36mHow to make Kubernetes rhyme with prod readiness - Tiffany Jernigan and Matthias Haeussler
35mWhat Does “Production Ready” Really Mean for a Kubernetes Cluster?
22mAnatomy of a production grade Kubernetes cluster
40mFrom dev to prod. One Year of Using Kubernetes in Production
19mKube Me This! Kubernetes Ideas and Best Practices
51mKubernetes for the Impatient
40mThe Good, the Bad, and the Ugly of Managing Production Systems with Kubernetes