For VMworld but it is agnostic really to any Kubernetes platform. Hopefully this will also give you the 101 on CI / CD Pipelines without confusing what they are and where you potentially use these processes already today.
A policy driven approach to protecting your Kubernetes applications and data is really something even from a virtualisation space we have been speaking about for a while at Veeam. The ability to move away or as well as those scheduled backups, when something happens take a backup or move some data.
The ability to deploy code and version code has been a de facto requirement and a reason we have CI/CD pipelines for our application development, but with Kubernetes in particular we are seeing a closer tie between code and data. In particular, code being deployed can affect and change your data, for that reason, we need to consider protecting that data as part of our Continous Development pipelines, In this session, we will focus on how we can incorporate backup actions into your pipeline to ensure that any code changes will start by creating a restore point be it a snapshot or an export to another external repository. We will then as part of a demo incorporate a failure scenario into the environment pipeline to simulate how a configmap can manipulate data to cause data loss. Then we need a way to bring the data back!
