Velero backups of vSphere persistent volumes fail on Kubernetes clusters version 1.20 or higher
search cancel

Velero backups of vSphere persistent volumes fail on Kubernetes clusters version 1.20 or higher

book

Article ID: 317047

calendar_today

Updated On:

Products

VMware Tanzu Kubernetes Grid Integrated (TKGi)

Issue/Introduction

Symptoms:
  • Velero backups of vSphere persistent volumes fail Kubernetes clusters version 1.20 or higher.
  • You see messages similar to the following when you describe the Velero backup:
time="2021-04-02T16:29:05Z" level=info msg="1 errors encountered backup up item" backup=velero/nginx-backup logSource="pkg/backup/
backup.go:427" name=nginx-deployment-66689547d-d7n6c
time="2021-04-02T16:29:05Z" level=error msg="Error backing up item" backup=velero/nginx-backup error="error executing custom action (groupResource=persistentvolumeclaims, namespace=nginx-example, name=nginx-logs): rpc error: code = Unknown desc = Failed during IsObjectBlocked check: Could not translate selfLink  to CRD name" logSource="pkg/backup/backup.go:431" name=nginx-deployment-66689547d-d7n6c
  • You are using the Velero Plugin for vSphere version 1.1.0 or lower.


Environment

VMware Tanzu Kubernetes Grid 1.x
VMware Tanzu Kubernetes Grid Plus 1.x

Resolution

This issue is resolved in the Velero Plugin for vSphere version 1.1.1 or higher.

Workaround:
You can work around this issue by passing the --feature-gates=RemoveSelfLink=false flag to the kube-apiserver at startup.