Whether you call it GitOps, Infrastructure-as-Code (IaC), or just using a CI/CD pipeline to automatically deploy changes to an application, I think we can all agree that moving to a model where your application and resource configuration is defined as code is beneficial to everyone involved. This code is usually saved in git, the most popular source version control system for cloud-native projects, and provides an automatic and verifiable change capture process, and simplifies application rollout. More importantly, it also prevents “snowflakes” where the configuration of a deployed application differs from the definition because of manual edits.

However, even with these powerful primitives available to developers and operators, the need for Backup and Disaster Recovery is as important as ever. The below post covers some of the core reasons why deploying a backup solution will be critical for safety and scale.

#kubernetes