Kubernetes Resiliency
summary
Covers concrete ways to make Kubernetes resilient with Azure AKS: use multiple availability zones, split system and user node pools with taints/tolerations, apply topologySpreadConstraints to enforce distribution, run etcd with odd quorum and regular backups, and enable metrics + Horizontal Pod Autoscaler or KEDA for event-driven scaling. Recommends Pod Disruption Budgets, resource requests over hard limits, separate liveness vs readiness endpoints, and monitor with Container Insights or Prometheus/Grafana.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:00Agenda
- 1:34Infrastructure
- 2:30Networking
- 3:39Availability Zones
- 6:48Node Pools
- 10:48Infrastructure Level
- 11:55Kubernetes Components
- 14:48Service Discovery
- 16:21Rate Limiting and Circuit Breaking
- 18:32Metric Server
- 19:39Horizontal Pod Autoscaling
- 21:42Event Driven Autoscaling
- 22:51Pod disruption budgets
- 24:29Resource requests and limits
- 27:05Quality of services
- 28:46Liveness Readiness probes
- 30:49Kubernetes web resources
- 35:01Kubernetes production best practices
- 38:58CPU limits
related talks
17mResilient Applications on Kubernetes
30mResilient Architectures on Amazon EKS: High Availability Patterns and Strategies
29mKubernetes Workload Resiliency in Action: Beyond Basics
59mKubernetes - going beyond the basics
39mKubernetes is awesome – but …
51mBuilding a Resilient Application Infrastructure on Kubernetes
42mImproving Availability for Stateful Applications in Kubernetes
01h 01mKubernetes – going beyond the basics
