Using Velero to Protect Cluster API
Cluster API (also known as CAPI) is, as you may already know, an effort within the upstream Kubernetes community to apply Kubernetes-style APIs to cluster lifecycle management—in short, to use Kubernetes to manage the lifecycle of Kubernetes clusters. If you’re unfamiliar with CAPI, I’d encourage you to check out my introduction to Cluster API before proceeding. In this post, I’m going to show you how to use Velero (formerly Heptio Ark) to backup and restore Cluster API objects so as to protect your organization against an unrecoverable issue on your Cluster API management cluster.
To be honest, this process is so straightforward it almost doesn’t need to be explained. In general, the process for backing up the CAPI management cluster looks like this:
- Pause CAPI reconciliation on the management cluster.
- Back up the CAPI resources.
- Resume CAPI reconciliation.
In the event of catastrophic failure, the recovery process looks like this:
- Restore from backup onto another management cluster.
- Resume CAPI reconciliation.
Let’s look at these steps in a bit more detail.
Pausing and Resuming Reconciliation
The process for pausing and resuming reconciliation of CAPI resources is outlined in this separate blog post. To summarize that post here for convenience, the Cluster Continue reading