Plan to Fail: A Good Captain Doesn’t Sail Without Life Rafts
summary
Live demo shows Velero backing a namespaced app to an S3-compatible bucket and restoring it into a separate cluster, proving full and selective restore workflows actually work. Discussion names critical items to save beyond etcd: persistent volumes, TLS certs, container registries and cloud account configs, and explains provider snapshot plugins for AWS/GCP/Azure and cross-cloud transfer via Restic. Crash scenarios and human-error replication are quantified by demo success and completed backup/restore logs.
AI-written summary · about
chapters (14)
- 0:00Disaster recovery planning intro
- 1:04Need for recovery plan
- 3:31Key elements of DR plan
- 4:35Data to protect in K8s
- 7:09Redundancy isn't enough
- 8:58Backup strategies for registries
- 10:49K8s backup solutions overview
- 14:23Demo setup prerequisites
- 16:15Backup with Velero
- 21:26Install Velero on cluster
- 24:26Restore cluster from backup
- 26:10Inspect backups locally
- 27:36Wrap-up and resources
- 27:58Q&A
related talks
33mPlan to Fail: A Good Captain Doesn’t Sail Without Life Rafts
30mIs Your Kubernetes Disaster Recovery Actually Ready?
32mSchroedingers Backup
31mKubernetes Backup and Migration Strategies with Velero
07mLightning Talk: Optimizing Kubernetes Multicluster Backup & Restore
33mNavigating Disaster Recovery in Kubernetes and Crossplane: Strategies and Tools for Managing Stateful Workloads with GitOps for Platform Teams
41mVelero: Back Up and Restore Your Kubernetes Applications (Cleanly)
35mDisaster Recovery for your Kubernetes Clusters