Objective
In this tutorial, we are using Velero to back up and restore an OVHcloud Managed Kubernetes cluster.
Velero is an open source tool to safely back up and restore, perform disaster recovery, and migrate Kubernetes cluster resources.
For cluster configuration backup, we are using our Public Cloud’s Swift Object Storage with the Swift S3 API as the storage backend for Velero. Velero uses the S3 protocol to store the cluster backups on an S3 compatible object storage.
For Persistent Volumes backups, we are using the CSI snapshot support for Velero that enables Velero to backup and restore CSI-backed volumes using the Kubernetes CSI Snapshot Beta APIs.
Before you begin
This tutorial assumes that you already have a working OVHcloud Managed Kubernetes cluster, and some basic knowledge of how to operate it. If you want to know more on those topics, please look at the deploying a Hello World application documentation.
Instructions
Creating the S3 bucket for Velero
Velero needs an S3 bucket as the storage backend to store data from your cluster. In this section, you will create your S3 bucket on OVHcloud Object Storage.
Preparing your working environment
Before creating your S3 bucket, you need to:
Setting the OpenStack environment variables
You should now have access to your OpenStack RC file, with a filename like<user_name>-openrc.sh, and the username and password for your OpenStack account.
Set the environment variables by sourcing the OpenStack RC file:
source <user_name>-openrc.sh
The shell will ask you for your OpenStack password:
$ source -openrc.sh
Please enter your OpenStack Password for project as user :
Creating EC2 credentials
S3 tokens are different. You need two parameters (access and secret) to generate an S3 token.
These credentials will be safely stored in Keystone. To generate them with python-openstack client, use the following command:
openstack ec2 credentials create
Please write down the access and secret parameters:
$ openstack ec2 credentials create
+------------+----------------------------------------------------------------------------------------------------------------------------+
| Field | Value
+------------+----------------------------------------------------------------------------------------------------------------------------+
| access | 5a4d8b8d88104123a862c527ede5a3d3
| links | {u'self': u'https://auth.cloud.ovh.net/v3/users/d74d05ff121b44bea9216495e7f0df61/credentials/OS-EC2/5a4d8b8d88104123a862c527ede5a3d3'}
| project_id | 20e124b71be141299e111ec26b1892fa
| secret | 925d5fcfcd9f436d8ffcb20548cc53a2
| trust_id | None
| user_id | d74d05ff121b44bea9216495e7f0df61
+------------+----------------------------------------------------------------------------------------------------------------------------+
Configuring awscli client
Install the awscli client:
pip3 install awscli awscli-plugin-endpoint
Save the following configuration for awscli into the ~/.aws/config file:
[plugins]
endpoint = awscli_plugin_endpoint
[profile default]
# region = <public_cloud_region_without_digit>
region = us-east-va-1 #for example
s3 =
endpoint_url = https://s3.<public_cloud_region_without_digit>.cloud.ovh.us
signature_version = s3v4
addressing_style = virtual
s3api =
endpoint_url = https://s3.<public_cloud_region_without_digit>.cloud.ovh.us
Create an S3 bucket for Velero
Create a new bucket:
aws --profile default s3 mb s3://velero-s3
List your buckets:
aws s3 ls
Installing Velero
We strongly recommend that you use an official release of Velero. The tarballs for each release contain the Velero command-line client. Expand the tarball and add it to your PATH.
Create a Velero-specific credentials file (credentials-velero) in your local directory:
[default]
aws_access_key_id=<AWS_ACCESS_KEY_ID>
aws_secret_access_key=<AWS_SECRET_ACCESS_KEY>
The <AWS_ACCESS_KEY_ID> and <AWS_SECRET_ACCESS_KEY> are the access and secret S3 credentials generated in the precedent step.
Install Velero, including all prerequisites, into the cluster and start the deployment. This will create a namespace called velero, and place a deployment named velero in it.
velero install \
--features=EnableCSI \
--provider aws \
--plugins velero/velero-plugin-for-aws:v1.6.0,velero/velero-plugin-for-csi:v0.4.0 \
--bucket <your bucket name> \
--secret-file ./credentials-velero \
--backup-location-config region=<public cloud region without digit>,s3ForcePathStyle="true",s3Url=https://s3.<public cloud region without digit>.cloud.ovh.net \
--snapshot-location-config region=<public cloud region without digit>,enableSharedConfig=true
In our case, with the cluster in the US-EAST-VA-1 region, that means:
velero install \
--features=EnableCSI \
--provider aws \
--plugins velero/velero-plugin-for-aws:v1.6.0,velero/velero-plugin-for-csi:v0.4.0 \
--bucket velero-s3 \
--secret-file ./credentials-velero \
--backup-location-config region=us-east-va-1,s3ForcePathStyle="true",s3Url=https://s3.us-east-va-1.cloud.ovh.net \
--snapshot-location-config region=us-east-va-1,enableSharedConfig=true
$ velero install \
--features=EnableCSI \
--provider aws \
--plugins velero/velero-plugin-for-aws:v1.6.0,velero/velero-plugin-for-csi:v0.4.0 \
--bucket velero-s3 \
--secret-file ./credentials-velero \
--backup-location-config region=us-east-va-1,s3ForcePathStyle="true",s3Url=https://s3.us-east-va-1.cloud.ovh.net \
--snapshot-location-config region=us-east-va-1,enableSharedConfig=true
CustomResourceDefinition/backups.velero.io: attempting to create resource
CustomResourceDefinition/backups.velero.io: attempting to create resource client
CustomResourceDefinition/backups.velero.io: created
CustomResourceDefinition/backupstoragelocations.velero.io: attempting to create resource
CustomResourceDefinition/backupstoragelocations.velero.io: attempting to create resource client
CustomResourceDefinition/backupstoragelocations.velero.io: created
CustomResourceDefinition/deletebackuprequests.velero.io: attempting to create resource
CustomResourceDefinition/deletebackuprequests.velero.io: attempting to create resource client
CustomResourceDefinition/deletebackuprequests.velero.io: created
[...]
VolumeSnapshotLocation/default: attempting to create resource
VolumeSnapshotLocation/default: attempting to create resource client
VolumeSnapshotLocation/default: created
Deployment/velero: attempting to create resource
Deployment/velero: attempting to create resource client
Deployment/velero: created
Velero is installed! ⛵ Use 'kubectl logs deployment/velero -n velero' to view the status.
In order to allow Velero to do Volume Snapshots, we need to deploy a new VolumeSnapshotClass. Create a velero-snapclass.yaml file with this content:
apiVersion: snapshot.storage.k8s.io/v1
deletionPolicy: Delete
driver: cinder.csi.openstack.org
kind: VolumeSnapshotClass
metadata:
name: csi-cinder-snapclass-in-use-v1-velero
labels:
velero.io/csi-volumesnapshot-class: "true"
parameters:
force-create: "true"
Apply the new class:
kubectl apply -f velero-snapclass.yaml
In our case, the result looks like this:
$ kubectl apply -f velero-snapclass.yaml volumesnapshotclass.snapshot.storage.k8s.io/csi-cinder-snapclass-in-use-v1-velero created $ kubectl get volumesnapshotclass --show-labels NAME DRIVER DELETIONPOLICY AGE LABELS csi-cinder-snapclass-in-use-v1 cinder.csi.openstack.org Delete 4h46m csi-cinder-snapclass-in-use-v1-velero cinder.csi.openstack.org Delete 5s velero.io/csi-volumesnapshot-class=true csi-cinder-snapclass-v1 cinder.csi.openstack.org Delete 4h46m
Verifying Velero is working without Persistent Volumes
To verify that Velero is working correctly, let’s test with one example deployment:
Copy the following code into an nginx-example-without-pv.yml file:
---
apiVersion: v1
kind: Namespace
metadata:
name: nginx-example
labels:
app: nginx
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx-deployment
namespace: nginx-example
spec:
replicas: 2
selector:
matchLabels:
app: nginx
template:
metadata:
labels:
app: nginx
spec:
containers:
- image: nginx:1.7.9
name: nginx
ports:
- containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
labels:
app: nginx
name: my-nginx
namespace: nginx-example
spec:
ports:
- port: 80
targetPort: 80
selector:
app: nginx
type: LoadBalancer
And apply it to your cluster:
kubectl apply -f nginx-example-without-pv.yml
Check that the Pods have been created:
kubectl get pod -n nginx-example
Create a backup of the namespace:
velero backup create nginx-backup --include-namespaces nginx-example
Verify that the backup is done:
velero get backup nginx-backup
Note: Wait until the status is Completed.
Simulate a disaster:
kubectl delete namespaces nginx-example
Restore the deleted namespace:
velero restore create --from-backup nginx-backup
Verify that the restore is correctly done:
kubectl get all -n nginx-example
In our case, the result looks like this:
$ kubectl apply -f nginx-example-without-pv.yml namespace/nginx-example created deployment.apps/nginx-deployment created service/my-nginx created $ kubectl get pod -n nginx-example NAME READY STATUS RESTARTS AGE nginx-deployment-84df99548d-h9hlb 1/1 Running 0 2m24s nginx-deployment-84df99548d-p8ktw 1/1 Running 0 2m19s $ velero backup create nginx-backup --include-namespaces nginx-example Backup request "nginx-backup" submitted successfully. Run `velero backup describe nginx-backup` or `velero backup logs nginx-backup` for more details. $ velero get backup nginx-backup NAME STATUS ERRORS WARNINGS CREATED EXPIRES STORAGE LOCATION SELECTOR nginx-backup Completed 0 1 2023-01-11 09:28:58 +0100 CET 29d default $ kubectl delete namespaces nginx-example namespace "nginx-example" deleted $ kubectl get all -n nginx-example No resources found in nginx-example namespace. $ velero restore create --from-backup nginx-backup Restore request "nginx-backup-20230111093134" submitted successfully. Run `velero restore describe nginx-backup-20230111093134` or `velero restore logs nginx-backup-20230111093134` for more details. $ velero restore logs nginx-backup-20230111093134 time="2023-01-11T08:31:36Z" level=info msg="starting restore" logSource="pkg/controller/restore_controller.go:478" restore=velero/nginx-backup-20230111093134 time="2023-01-11T08:31:36Z" level=info msg="Starting restore of backup velero/nginx-backup" logSource="pkg/restore/restore.go:392" restore=velero/nginx-backup-20230111093134 time="2023-01-11T08:31:36Z" level=info msg="Resource 'volumesnapshotclasses.snapshot.storage.k8s.io' will be restored at cluster scope" logSource="pkg/restore/restore.go:1891" restore=velero/nginx-backup-20230111093134 time="2023-01-11T08:31:36Z" level=info msg="Resource 'volumesnapshotcontents.snapshot.storage.k8s.io' will be restored at cluster scope" logSource="pkg/restore/restore.go:1891" restore=velero/nginx-backup-20230111093134 [...] time="2023-01-11T08:31:37Z" level=warning msg="Cluster resource restore warning: could not restore, VolumeSnapshotContent \"snapcontent-83dc003f-7ed2-47c3-9442-61b48686cf78\" already exists. Warning: the in-cluster version is different than the backed-up version." logSource="pkg/controller/restore_controller.go:511" restore=velero/nginx-backup-20230111093134 time="2023-01-11T08:31:37Z" level=info msg="restore completed" logSource="pkg/controller/restore_controller.go:518" restore=velero/nginx-backup-20230111093134 $ kubectl get all -n nginx-example NAME READY STATUS RESTARTS AGE pod/nginx-deployment-84df99548d-h9hlb 1/1 Running 0 2m39s pod/nginx-deployment-84df99548d-p8ktw 1/1 Running 0 2m39s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/my-nginx LoadBalancer 10.3.120.98 80:30445/TCP 2m39s service/nginx-service LoadBalancer 10.3.209.170 80:30045/TCP 2m39s NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/nginx-deployment 2/2 2 2 2m39s NAME DESIRED CURRENT READY AGE replicaset.apps/nginx-deployment-5bfc8c9f6f 0 0 0 2m39s replicaset.apps/nginx-deployment-84df99548d 2 2 2 2m39s
Before continuing, clean the nginx-example namespace:
kubectl delete namespace nginx-example
Verifying Velero is working with Persistent Volumes
To verify that Velero is working correctly with Volume Snapshots of Persistent Volumes, let’s test with one example deployment:
Copy the following code into an nginx-example-with-pv.yml file:
---
apiVersion: v1
kind: Namespace
metadata:
name: nginx-example
labels:
app: nginx
---
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: nginx-logs
namespace: nginx-example
labels:
app: nginx
spec:
storageClassName: csi-cinder-high-speed
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: nginx-deployment
namespace: nginx-example
spec:
strategy:
type: Recreate
replicas: 1
selector:
matchLabels:
app: nginx
template:
metadata:
labels:
app: nginx
spec:
volumes:
- name: nginx-logs
persistentVolumeClaim:
claimName: nginx-logs
containers:
- image: nginx:1.7.9
name: nginx
ports:
- containerPort: 80
volumeMounts:
- mountPath: "/var/log/nginx"
name: nginx-logs
readOnly: false
---
apiVersion: v1
kind: Service
metadata:
labels:
app: nginx
name: nginx-service
namespace: nginx-example
spec:
ports:
- port: 80
targetPort: 80
selector:
app: nginx
type: LoadBalancer
Apply it to the cluster:
kubectl apply -f nginx-example-with-pv.yml
Note: Pay attention to the deployment part of this manifest. You will see that we have defined a .spec.strategy.type. It specifies the strategy used to replace old Pods with new ones, and we have set it to Recreate so that all existing Pods are killed before new ones are created.
We do so because the Storage Class we are using, csi-cinder-high-speed, only supports a ReadWriteOnce, so we can only have one pod writing on the Persistent Volume at any given time.
Wait until you get an external IP:
kubectl -n nginx-example get svc nginx-service -w
When you have a Load Balancer External IP, save it:
export LB_IP=$(kubectl -n nginx-example get svc nginx-service -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
Make some calls to the URL to generate some access logs:
curl -I $LB_IP
You should have a result like this:
$ kubectl apply -f nginx-example-with-pv.yml namespace/nginx-example unchanged persistentvolumeclaim/nginx-logs created deployment.apps/nginx-deployment configured service/nginx-service created $ kubectl -n nginx-example get svc nginx-service -w NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE nginx-service LoadBalancer 10.3.219.64 80:31157/TCP 26s nginx-service LoadBalancer 10.3.219.64 80:31157/TCP 80s nginx-service LoadBalancer 10.3.219.64 51.210.XXX.XX 80:31157/TCP 80s nginx-service LoadBalancer 10.3.219.64 51.210.XXX.XX 80:31157/TCP 83s $ export LB_IP=$(kubectl -n nginx-example get svc nginx-service -o jsonpath='{.status.loadBalancer.ingress[0].ip}') $ echo $LB_IP 51.210.XXX.XX $ curl -I $LB_IP HTTP/1.1 200 OK Server: nginx/1.7.9 Date: Wed, 11 Jan 2023 08:37:30 GMT Content-Type: text/html Content-Length: 612 Last-Modified: Tue, 23 Dec 2014 16:25:09 GMT Connection: keep-alive ETag: "54999765-264" Accept-Ranges: bytes $ curl -I $LB_IP HTTP/1.1 200 OK Server: nginx/1.7.9 Date: Wed, 11 Jan 2023 08:37:33 GMT Content-Type: text/html Content-Length: 612 Last-Modified: Tue, 23 Dec 2014 16:25:09 GMT Connection: keep-alive ETag: "54999765-264" Accept-Ranges: bytes
Now we need to connect to the Pod to read the log file and verify that our logs are written.
First, get the name of the Nginx-running pod:
exportPOD_NAME=$(kubectl -n nginx-example get pods -o name)
Then connect to it and view your access logs:
kubectl -n nginx-example exec$POD_NAME -c nginx -- cat /var/log/nginx/access.log
You should have a result like this:
$ export POD_NAME=$(kubectl -n nginx-example get pods -o name) $ echo $POD_NAME pod/nginx-deployment-5bfc8c9f6f-xkw5x $ kubectl -n nginx-example exec $POD_NAME -c nginx -- cat /var/log/nginx/access.log xxx.xxx.xxx.xxx - - [11/Jan/2023:08:37:30 +0000] "HEAD / HTTP/1.1" 200 0 "-" "curl/7.64.1" "-" xxx.xxx.xxx.xxx - - [11/Jan/2023:08:37:33 +0000] "HEAD / HTTP/1.1" 200 0 "-" "curl/7.64.1" "-"
Now we can ask Velero to do the backup of the namespace:
velero backup create nginx-backup-with-pv --include-namespaces nginx-example --wait
Check that the backup has finished successfully:
velero backup get nginx-backup-with-pv
Describe the backup to confirm that the CSI volumesnapshots were included in the backup:
velero describe backup nginx-backup-with-pv --details --features=EnableCSI
Simulate a disaster:
kubectl delete namespace nginx-example
Restore the deleted namespace:
velero restore create --from-backup nginx-backup-with-pv --wait
Verify that the restore is correctly done:
kubectl get all -n nginx-example
kubectl get pvc -n nginx-example
Now we need to connect to the new Pod to read the log file and verify that our logs are written like before.
Get the name of the Nginx running pod:
exportPOD_NAME=$(kubectl -n nginx-example get pods -o name)
Then connect to it and view your access logs:
kubectl -n nginx-example exec$POD_NAME -c nginx -- cat /var/log/nginx/access.log
You should have a result like this:
$ velero backup create nginx-backup-with-pv --include-namespaces nginx-example --wait Backup request "nginx-backup-with-pv" submitted successfully. Waiting for backup to complete. You may safely press ctrl-c to stop waiting - your backup will continue in the background. ........ Backup completed with status: Completed. You may check for more information using the commands `velero backup describe nginx-backup-with-pv` and `velero backup logs nginx-backup-with-pv`. $ velero backup get nginx-backup-with-pv NAME STATUS ERRORS WARNINGS CREATED EXPIRES STORAGE LOCATION SELECTOR nginx-backup-with-pv Completed 0 1 2023-01-11 09:38:39 +0100 CET 29d default $ velero describe backup nginx-backup-with-pv --details --features=EnableCSI Name: nginx-backup-with-pv Namespace: velero Labels: velero.io/storage-location=default Annotations: velero.io/source-cluster-k8s-gitversion=v1.24.8 velero.io/source-cluster-k8s-major-version=1 velero.io/source-cluster-k8s-minor-version=24 Phase: Completed Errors: 0 Warnings: 1 Namespaces: Included: nginx-example Excluded: Resources: Included: * Excluded: Cluster-scoped: auto Label selector: Storage Location: default Velero-Native Snapshot PVs: auto TTL: 720h0m0s Hooks: Backup Format Version: 1.1.0 Started: 2023-01-11 09:38:39 +0100 CET Completed: 2023-01-11 09:38:53 +0100 CET Expiration: 2023-02-10 09:38:39 +0100 CET Total items to be backed up: 28 Items backed up: 28 Resource List: apps/v1/Deployment: - nginx-example/nginx-deployment apps/v1/ReplicaSet: - nginx-example/nginx-deployment-5bfc8c9f6f discovery.k8s.io/v1/EndpointSlice: - nginx-example/nginx-service-8zztd snapshot.storage.k8s.io/v1/VolumeSnapshot: - nginx-example/velero-nginx-logs-4mzqj snapshot.storage.k8s.io/v1/VolumeSnapshotClass: - csi-cinder-snapclass-in-use-v1-velero snapshot.storage.k8s.io/v1/VolumeSnapshotContent: - snapcontent-a94596ac-53e8-4dbd-82ab-4b2b2059f9ad v1/ConfigMap: - nginx-example/kube-root-ca.crt v1/Endpoints: - nginx-example/nginx-service v1/Event: - nginx-example/nginx-deployment-5bfc8c9f6f-wfh2s.17393436adcb2afc - nginx-example/nginx-deployment-5bfc8c9f6f-wfh2s.17393437118d0de4 - nginx-example/nginx-deployment-5bfc8c9f6f-wfh2s.173934386fe43eb6 - nginx-example/nginx-deployment-5bfc8c9f6f-wfh2s.17393439eaee38ad - nginx-example/nginx-deployment-5bfc8c9f6f-wfh2s.1739343a473097ed - nginx-example/nginx-deployment-5bfc8c9f6f-wfh2s.1739343a4b321cbb - nginx-example/nginx-deployment-5bfc8c9f6f-wfh2s.1739343a579c4298 - nginx-example/nginx-deployment-5bfc8c9f6f.17393436adb1ca3e - nginx-example/nginx-deployment.17393436aca15492 - nginx-example/nginx-logs.17393436a42eebba - nginx-example/nginx-logs.17393436a43b2735 - nginx-example/nginx-logs.17393436cd9041ea - nginx-example/nginx-service.17393436b64016dd - nginx-example/nginx-service.17393442dbc725bd v1/Namespace: - nginx-example v1/PersistentVolume: - ovh-managed-kubernetes-dmhe43-pvc-310bd5e6-b4ef-41eb-8960-17a99c837355 v1/PersistentVolumeClaim: - nginx-example/nginx-logs v1/Pod: - nginx-example/nginx-deployment-5bfc8c9f6f-wfh2s v1/Service: - nginx-example/nginx-service v1/ServiceAccount: - nginx-example/default Velero-Native Snapshots: CSI Volume Snapshots: Snapshot Content Name: snapcontent-a94596ac-53e8-4dbd-82ab-4b2b2059f9ad Storage Snapshot ID: e72e2844-d5e5-4829-96c7-8c2cd80b475b Snapshot Size (bytes): 1073741824 Ready to use: true $ kubectl delete namespace nginx-example namespace "nginx-example" deleted $ velero restore create --from-backup nginx-backup-with-pv --wait Restore request "nginx-backup-with-pv-20230111094040" submitted successfully. Waiting for restore to complete. You may safely press ctrl-c to stop waiting - your restore will continue in the background. . Restore completed with status: Completed. You may check for more information using the commands `velero restore describe nginx-backup-with-pv-20230111094040` and `velero restore logs nginx-backup-with-pv-20230111094040`. $ kubectl get all -n nginx-example NAME READY STATUS RESTARTS AGE pod/nginx-deployment-5bfc8c9f6f-wfh2s 1/1 Running 0 22s NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/nginx-service LoadBalancer 10.3.xxx.xxx 80:31456/TCP 22s NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/nginx-deployment 1/1 1 1 22s NAME DESIRED CURRENT READY AGE replicaset.apps/nginx-deployment-5bfc8c9f6f 1 1 1 22s $ export POD_NAME=$(kubectl -n nginx-example get pods -o name) $ kubectl -n nginx-example exec $POD_NAME -c nginx -- cat /var/log/nginx/access.log 141.94.167.92 - - [11/Jan/2023:08:37:30 +0000] "HEAD / HTTP/1.1" 200 0 "-" "curl/7.64.1" "-" 141.94.167.92 - - [11/Jan/2023:08:37:33 +0000] "HEAD / HTTP/1.1" 200 0 "-" "curl/7.64.1" "-"
Your namespace with resources and PVC have been correctly restored.
Scheduling backup with Velero
With Velero, you can schedule backups regularly, which is a good practice for disaster recovery.
In this guide, you will create a schedule Velero resource that will create regular backups.
Copy the following code into a schedule.yml file:
apiVersion: velero.io/v1
kind: Schedule
metadata:
name: daily-snapshot
namespace: velero
spec:
schedule: '15 0 * * *' # Every day at 00:15 am
template:
defaultVolumesToRestic: false
includedNamespaces:
- nginx-example
ttl:168h0m0s # Keep the backup 7 days
storageLocation:default
Apply it to the cluster:
kubectl apply -f schedule.yml
Verify that the schedule is correctly created:
velero schedule get
Wait several minutes and verify that a backup has been created automatically:
velero backup get
You should have a result like this:
$ velero schedule get NAME STATUS CREATED SCHEDULE BACKUP TTL LAST BACKUP SELECTOR daily-snapshot Enabled 2023-01-11 09:43:00 +0100 CET 15 0 * * * 168h0m0s 9h ago $ velero backup get NAME STATUS ERRORS WARNINGS CREATED EXPIRES STORAGE LOCATION SELECTOR daily-snapshot-20230111084430 Completed 0 1 2023-01-11 09:44:30 +0100 CET 6d default
Cleanup
Clean the nginx-example namespace:
kubectl delete namespace nginx-example
Clean the Velero schedule:
velero schedule delete daily-snapshot
Clean the existing Velero backup:
velero backup delete nginx-backup
velero backup delete nginx-backup-with-pv
Where do we go from here
Now you have a working Velero on your cluster. Please refer to the official Velero documentation to learn its uses including scheduling backups, using pre- and post-backup hooks, and other matters.