Level 2 - Automation

Automating checkpoint/migrate/restore!

Now that you've completed a simple manual checkpoint/restore, from one node to another, we can make things interesting via automations.

Cedana gives you access to automations via Policies, which can be created through the UI.

We have more policies in the works, but the most basic one is the heartbeat policy, which creates a heartbeat checkpoint for a specified target resource (a Pod) or a set of resources in a namespace every predefined interval.

Restoring from these is as simple as doing it from the UI, or simply reapplying the Job yaml (see Managing Kubernetes Jobsfor more information).

The best way to try out the automation is to test it for yourself!

Deleting via EC2 console (as shown in the video below) takes some time to propagate, so try deleting from k9s or kubectl to see the instant restore!

See the video below for a demonstration showing automatic restores on node termination on EKS from the EC2 console.

Moving Past Pods

The cordon-based policy works best for pods, but if you're running other CRDs or kinds that have their own lifecycles, it can conflict. Thankfully, cedana has a seamless solution for job support! See Managing Kubernetes Jobsfor more information on automating jobs with Cedana.