How to make kubernetes rhyme with prod readiness
summary
Checklist of what's missing between a Kubernetes cluster and a production cluster: decide cloud vs on‑prem and managed vs self‑hosted, add logging/metrics and backups (Velero), pick an Ingress controller or Gateway API and enforce NetworkPolicies and RBAC with PodSecurity standards and cert‑management (cert‑manager), instrument with Prometheus/Grafana and tracing (Jaeger/OpenTelemetry), consider service mesh (Istio, Linkerd) or eBPF alternatives, and use repeatable delivery and templating like kustomize, Helm, Carvel and GitOps ArgoCD, Flux to close the gap.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:19Production readiness
- 4:52Kubernetes basics
- 9:49Cluster to production
- 12:36Networking essentials
- 15:26Observability in clusters
- 16:28Security practices
- 19:01Workload stability
- 22:31Summary
- 24:17CNCF tools
- 28:51Tools overview
- 30:54Managed vs self-hosted
- 31:15Q&A
related talks
29mHow 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
39mKubernetes is awesome – but …
41mKubernetes on-premises, why you don't want to do it?
40mFrom dev to prod. One Year of Using Kubernetes in Production
19mKube Me This! Kubernetes Ideas and Best Practices