Velero backup pod in CrashLoopBackOff status when installing on supervisor cluster
Article ID: 417172
Updated On:
Products
Issue/Introduction
Customer is trying to configure Velero to backup Tanzu Kubenetes clusters but they are hitting into some issues where the Velero in the supervisor cannot start up but just getting into CLBO without any error.
Velero Pods are in "CrashLoopBackOff" status.
# kubectl get pods -n velero
NAME READY STATUS RESTARTS AGE
velero-xxxxxxxxxx-xx.xxx 1/1 CrashLoopBackOff 0 30m
Environment
Velero 1.8.1
Velero Plugin for AWS 1.6.0
Velero Plugin for vSphere 1.5.6
Velero vSphere Operator 1.6.1 embedded
Data Manager version 1.2.0
vSphere 8.0U3
Cause
The reason is that customer is using Velero Plugin for AWS in the environment, it is the AWS object store and volume snapshotter plugin that lets Velero back up and restore Tanzu Kubernetes (TKG/TKGS) cluster resources and persistent volumes to AWS S3 and EBS.
Resolution
Customer changed the version of Velero vSphere Operator CLI to 1.6.1 which resolved the issue.
Steps followed :
1.Create a supervisor namespace for Velero instance via vSphere UI.
2.Create Velero vSphere Plugin Config
3.Run Velero vSphere Operator CLI, velero-vsphere, to install Velero into the same namespace created in the previous step.
Additional Information
Please refer to github link for compatibility matrix
https://github.com/vmware-tanzu/velero-plugin-for-vsphere/blob/main/docs/supervisor.md#compatibility
Installing Velero on Supervisor cluster guidance:
https://github.com/vmware-tanzu/velero-plugin-for-vsphere/blob/main/docs/velero-vsphere-operator-user-manual.md#installing-velero-on-supervisor-cluster
Feedback
