I'm have deployed velero in my k8s 1.18 aws self managed cluster using velero client. Velero pods are running. But backups are failing because backupstoragelocation state/phase is in "unknown".
IAM with enough permissions are attached. S3 bucket is accessible. I even see the failed backups in S3 bucket. Yet the velero is throwing the backup to be failed and backupstoragelocation state is "unknown". I'm not able to get the backups logs from velero.
velero version used : v1.11.0 k8s version : 1.18
I'm not able to understand the cause of this behaviour. Please help.
Below is the error from pod logs and backupstoragelocation details
kubectl get backupstoragelocation -A
NAMESPACE NAME PHASE LAST VALIDATED AGE DEFAULT
cloudops default 67s true
kubectl get po -A -o wide | grep velero
cloudops velero-8bf55bb89-xxx 1/1 Running 0 77s xx ip-xx.us-west-2.compute.internal <none> <none>
cloudops velero-backup-xxx 0/1 Completed 0 81s xx ip-xx.us-west-2.compute.internal <none> <none>
logs
level=info msg="Validating BackupStorageLocation" backup-storage-location=cloudops/default controller=backup-storage-location logSource="pkg/controller/backup_storage_location_controller.go:152"
time="2023-07-19T06:56:38Z" level=info msg="BackupStorageLocations is valid, marking as available" backup-storage-location=cloudops/default controller=backup-storage-location logSource="pkg/controller/backup_storage_location_controller.go:137"
time="2023-07-19T06:56:38Z" level=error msg="Current BackupStorageLocations available/unavailable/unknown: 0/0/1)" controller=backup-storage-location logSource="pkg/controller/backup_storage_location_controller.go:194"
I0719 06:56:40.505322 1 request.go:690] Waited for 1.046154724s due to client-side throttling, not priority and fairness, request:
I have tried Cleaning up the old velero resources and performed fresh installation which didnot work.
