I’m trying to install velero and test backups. I’m using kube2Iam instead of using credentials. I followed this guide to setup kube2iam and velero.

I’m getting Failed error and when I describe the backup I see following error Backup Volumes: <error getting backup volume info: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline>

I used helm to install velero.

Here is my velero-values.yaml

podAnnotations:
  iam.amazonaws.com/role: arn:aws:iam::1234567890:role/velero

configuration:
  backupStorageLocation:
    - name: aws
      default: true
      provider: aws
      bucket: velero-test123
      config:
        region: eu-central-1
  volumeSnapshotLocation:
    - name: aws
      provider: aws
      config:
        region: eu-central-1

initContainers:
  - name: velero-plugin-for-aws
    image: velero/velero-plugin-for-aws:v1.0.0
    imagePullPolicy: IfNotPresent
    volumeMounts:
      - mountPath: /target
        name: plugins

Then I installed velero using the following command

helm install backup   --namespace kube-system   -f velero-values.yaml   vmware-tanzu/velero

Then I created a new backup

[ec2-user@ip-10-15-1-155 ~]$ velero -n kube-system backup create test4

Backup request "test4" submitted successfully.

But it shows it failed

[ec2-user@ip-10-15-1-155 ~]$ velero -n kube-system backup get
NAME    STATUS             ERRORS   WARNINGS   CREATED                         EXPIRES   STORAGE LOCATION   SELECTOR
test4   Failed             0        0          2024-07-11 15:49:38 +0000 UTC   29d       aws                <none>

Describing shows a weird error and I can’t find any fix.

[ec2-user@ip-10-15-1-155 ~]$ velero backup describe test4 -n kube-system

Name:         test4
Namespace:    kube-system
Labels:       velero.io/storage-location=aws
Annotations:  velero.io/resource-timeout=10m0s
              velero.io/source-cluster-k8s-gitversion=v1.29.4-eks-036c24b
              velero.io/source-cluster-k8s-major-version=1
              velero.io/source-cluster-k8s-minor-version=29+

Phase:  Failed (run `velero backup logs test4` for more information)


Namespaces:
  Included:  *
  Excluded:  <none>

Resources:
  Included:        *
  Excluded:        <none>
  Cluster-scoped:  auto

Label selector:  <none>

Or label selector:  <none>

Storage Location:  aws

Velero-Native Snapshot PVs:  auto
Snapshot Move Data:          false
Data Mover:                  velero

TTL:  720h0m0s

CSISnapshotTimeout:    10m0s
ItemOperationTimeout:  4h0m0s

Hooks:  <none>

Backup Format Version:  1.1.0

Started:    2024-07-11 15:49:38 +0000 UTC
Completed:  <n/a>

Expiration:  2024-08-10 15:49:38 +0000 UTC

Backup Volumes:
  <error getting backup volume info: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline>

velero backup logs test4` doesn’t return anything.

[ec2-user@ip-10-15-1-155 ~]$ velero backup logs test4
An error occurred: backup "test4" does not exist

Any idea why I can’t create backups using velero?