Skip to content


Don't be like Cameron. Backup your stuff.

Waitasec, what happened to "cattle 🐮, not pets"? Why should you need backup in your cluster?

Ha. good question. If you're happily running Kubernetes in a cloud provider and using managed services for all your stateful workloads (managed databases, etc) then you don't need backup.

If, on the other hand, you're actually using the persistence you deployed earlier, presumably some of what you persist is important to you, and you'd want to back it up in the event of a disaster (or you need to roll back a database upgrade!).

The only backup solution I've put in place thus far is Velero, but this index page will be expanded to more options as they become available.

For your backup needs, I present, Velero, by VMWare:

Chef's notes 📓

///Footnotes Go Here///

Tip your waiter (sponsor) 👏

Did you receive excellent service? Want to compliment the chef? (..and support development of current and future recipes!) Sponsor me on Github / Ko-Fi / Patreon, or see the contribute page for more (free or paid) ways to say thank you! 👏

Employ your chef (engage) 🤝

Is this too much of a geeky PITA? Do you just want results, stat? I do this for a living - I'm a full-time Kubernetes contractor, providing consulting and engineering expertise to businesses needing short-term, short-notice support in the cloud-native space, including AWS/Azure/GKE, Kubernetes, CI/CD and automation.

Learn more about working with me here.

Flirt with waiter (subscribe) 💌

Want to know now when this recipe gets updated, or when future recipes are added? Subscribe to the RSS feed, or leave your email address below, and we'll keep you updated.

Your comments? 💬