Using third party Backup in Trident Kubernetes Cluster causes PVC creation timeouts
Applies to
Trident for Kubernetes/Openshift up to 23.10
Issue
New PVC creations are delayed a very long time after running Backups on PODs and their PVCs:
- errors often seen are "context deadline exceeded" for PVC creations - see also Trident mount volume failed with the error "context deadline exceeded"
- additionally seen may be Trident error "client rate limiter Wait returned an error: context canceled" due to Kubernetes and Trident (23.04+) request rate limiters
- cleanup of previous clone PVCs and Snapshots is delayed for some of the backed up PVCs, causing them to be in deleting state