Plan to Fail: A Good Captain Doesn’t Sail Without Life Rafts
summary
Claim: disaster recovery is practical for every org now that public cloud and cloud-native tools lower cost and complexity. Concrete items to back up: etcd and CRDs, persistent volumes and TLS certificates, container registries and DNS/ cloud account configs. Demo uses Velero with a local MinIO S3 endpoint (port 9000), creates backup "acme-dump" of namespace name-example, restores into a staging cluster and verifies with curl — the app responds. Velero supports provider snapshot plugins and Restic for cross-cloud PV restores.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:09Presenters
- 1:33Why do you need a recovery plan?
- 2:27Elements of a Disaster Recovery Plan
- 4:22What to protect
- 5:25Critical items outside etcd
- 7:04Redundancy alone is not enough
- 7:50Container Images, Helm charts, other binaries and installables
- 10:35Use cases for Kubernetes backup solutions
- 11:06some Kubernetes open source backup options
- 28:05Contacts
related talks
33mPlan to Fail: A Good Captain Doesn’t Sail Without Life Rafts
30mIs Your Kubernetes Disaster Recovery Actually Ready?
33mNavigating Disaster Recovery in Kubernetes and Crossplane: Strategies and Tools for Managing Stateful Workloads with GitOps for Platform Teams
32mSchroedingers Backup
35mDisaster Recovery for your Kubernetes Clusters
25mAutomating Disaster Recovery: The Ultimate Reliability Challenge
31mKubernetes Backup and Migration Strategies with Velero
54mFive hybrid cloud backup and disaster recovery mistakes to avoid