Velero Upgrade Crds Container Back-off

[allwin-winfred]

Hello,
I'm running Velero on EKS (1.28) while installing Velero using the helm chart I'm facing an Issue in the Pod back-off restart container,
also, I'm deploying this chart using Terraform,
In the terraform console facing this error,
│ Error: release velero failed, and has been uninstalled due to atomic being set: failed pre-install: job failed: BackoffLimitExceeded

Then I inspected the Velero pod while installing it says below the error,

kubectl logs -n velero velero-upgrade-crds-lf5j9

Defaulted container "velero" out of: velero, kubectl (init)
->/tmp/sh: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /tmp/sh)

Would anyone be able to help with this issue?

[allwin-winfred]

After discovering that setting the following in my values.yaml allowed me to overcome the issue,
I realized that I was using Debian 11, but the default latest kubectl image OS was Debian 12.
This caused an error, but I managed to fix it.

kubectl:
  image:
    repository: docker.io/bitnami/kubectl
    tag: 1.27.11-debian-11-r5