On this talk we'll see how to do a disaster recovery from our dearest Kubernetes cluster and workloads. We'll review how Velero can help us on that and we'll show some hands on recovering a oh shit moment in our Kubernetes cluster.

1. Kubernetes Backup and Migration
Strategies with Velero

2. AGENDA
Use Cases Velero
Velero Components
Backup/Restore Data
Generic Workflow
Demo
Disaster Recovery
Data Migration
Conclusions

3. DISASTER
RECOVERY
DATA
INTEGRITY
DATA
MIGRATION
USE CASES
K8S BACKUP & MIGRATION STRATEGIES WITH VELERO

4. VELERO CLI
KUBERNETES CLUSTER
RESTIC
DAEMONSET
VELERO SERVER
CONTROLLER
VELERO
COMPONENTS

5. DATA
Kubernetes API Discovery
Backups in cloud object storage
ETCD
Cloud Provider Snapshot APIs
Agnostic File System level
backups (Restic)
PERSISTENT VOLUMES

6. DATA
Schedule backups
Filtering by multiple fields
FLEXIBILITY
Plugins
Hooks
EXTENSIBILITY

7. Using the Velero CLI, the user creates a Backup
custom resource using the Kubernetes API. The
instruction accept filtering by namespace, resource or
labelling, for instance `velero backup create cluster
--include-namespace ghost --wait`.
01
The Velero Controller notice about the new Backup
resource and validated the command.
The Velero Controller starts the backup process. It
queries the Kubernetes API to backup the resources.
The Velero Controller push the backup file to a cloud
object storage. Besides, it creates snapshots using
the cloud Snapshot API of any existing PV. The
backup process finished after upload the file to the
cloud object storage.
Using the Velero CLI, the user creates a
Restore custom restore using the Kubernetes
API. The instruction accept filtering by
namespace, resource or labelling, for instance
to restore from the sample above `velero
restore create --from-backup cluster
--include-namespace ghost`.
The Velero Controller notices about the new
Restore resource, validates the command and
start pulling the data from the cloud object
storage.
02
03
04
05 06
The Velero Controller restores the resources
querying the Kubernetes API to restore the
resources. The restore process finished after
deploying the pull data to the Kubernetes API.
07
01
KUBERNETES CLUSTER
VELERO WORKFLOW
GENERIC DIAGRAM
CREATE BACKUP
RESOURCE LIST RESOURCES PUSH BACKUP DATA
BACKUP
PULL BACKUP DATA
04
05
RESTORE
02
CREATE RESTORE
RESOURCE RESTORE RESOURCES
KUBERNETES CLUSTER
api
07
api
VELERO SERVER
CONTROLLER
03
VELERO SERVER
CONTROLLER
06

8. DEMO

9. VELERO WORKFLOW
DISASTER RECOVERY
Using the Velero CLI, the user creates a Backup custom
resource on EKS Cluster 1 using the Kubernetes API. The
instruction accept filtering by namespace, resource or
labelling, for instance `velero backup create cluster1
--include-namespace ghost --wait`.
01
The Velero Controller notice about the new Backup
resource and validated the command.
The Velero Controller starts the backup process. It
queries the Kubernetes API to backup the resources.
The Velero Controller push the backup file to a cloud
object storage. Besides, it creates snapshots using
the cloud Snapshot API of any existing PV. The
backup process finished after upload the file to the
cloud object storage.
Using the Velero CLI, the user creates a
Restore custom restore on EKS Cluster 2 using
the Kubernetes API. The instruction accept
filtering by namespace, resource or labelling,
for instance to restore from the sample above
`velero restore create --from-backup cluster1
--include-namespace ghost`.
The Velero Controller notices about the new
Restore resource, validates the command and start
pulling the data from the cloud object storage.
02
03
04
05 06
The Velero Controller restores the resources
querying the Kubernetes API to restore the
resources. The restore process finished after
deploying the pull data to the Kubernetes API. Data
from cluster1 has been recovered on cluster2.
07
01
05
BACKUP
RESTORE
EKS KUBERNETES CLUSTER 1
CREATE BACKUP
RESOURCE LIST RESOURCES PUSH BACKUP DATA
PULL BACKUP DATA
04
02
CREATE RESTORE
RESOURCE RESTORE RESOURCES
EKS KUBERNETES CLUSTER 2
api
07
api
VELERO SERVER
CONTROLLER
03
VELERO SERVER
CONTROLLER
06

10. VELERO WORKFLOW
DATA MIGRATION
Using the Velero CLI, the user creates a Backup custom
resource on EKS Cluster2 using the Kubernetes API.
The instruction accept filtering by namespace, resource
or labelling, for instance `velero backup create cluster2
--include-namespace ghost --wait`.
01
The Velero Controller notice about the new Backup
resource and validated the command.
The Velero Controller starts the backup process. It
queries the Kubernetes API to backup the resources.
Velero ensures a restic repository exists for the pod's
namespace. Velero creates a PodVolumeBackup
custom resource per volume listed in the pod
annotation. The main Velero process waits for the
PodVolumeBackup resources to complete or fail.
The Velero Controller push the backup file to a cloud
object storage. This file would be used for restores.
Using the Velero CLI, the user creates a
Restore custom restore on GKE cluster3 using
the Kubernetes API. The instruction accept
filtering by namespace, resource or labelling,
for instance to restore from the sample above
`velero restore create --from-backup cluster2
--include-namespace ghost`.
The Velero Controller notices about the new Restore
resource, validates the command and start pulling the
data from the cloud object storage. Velero creates a
PodVolumeRestore custom resource for each volume
to be restored in the pod.
02
03 04
05
06
The Velero Controller waits for each PodVolumeRestore
resource to complete or fail. It restores the resources
querying the Kubernetes API to restore the resources.
The restore process finished after deploying the pull data
to the Kubernetes API.
07
01
05
BACKUP
RESTORE
EKS KUBERNETES CLUSTER 2
CREATE BACKUP
RESOURCE PUSH BACKUP DATA
PULL BACKUP DATA
04
02
CREATE RESTORE
RESOURCE RESTORE RESOURCES
GKE KUBERNETES CLUSTER 3
api
07
api
VELERO SERVER
CONTROLLER
03
RESTIC
DAEMONSET
VELERO SERVER
CONTROLLER
06
RESTIC
DAEMONSET

11. SHOWTIME

12. DISASTER
RECOVERY
DATA
INTEGRITY
DATA
MIGRATION
CONCLUSIONS
K8S BACKUP & MIGRATION STRATEGIES WITH VELERO

13. ramiroalvfer.dev
github.com/empathyco/platform-velero-showcases
Get more info in