JenTing

> Forgot to update. Already resolved the issue. How about with my other concern? That's my issue now Could you please describe what's the rest concerns?

> Any updates on this? Could you please check the rendered template includes the `AZURE_CREDENTIALS_FILE` as `/credentials/cloud`? https://github.com/vmware-tanzu/helm-charts/blob/ae05805/charts/velero/templates/deployment.yaml#L162-L163

Could you please: 1. check the Secret resource created? 2. log in to the Velero pod to see if the `/credentials/cloud` existed?

I didn't have this experience before, but I believe someone in the community has the answer for you.

Any reason you're using old Velero and azure plug-in version?

Which Pods? Velero server?

Could you try this one https://github.com/vmware-tanzu/velero/blob/main/config/crd/v1/bases/velero.io_restores.yaml?

I see, would you mind try kubeadm or k3s or other Kubernetes distro with the same version `1.21.2`.

I think there must be something wrong with the restores.yaml manifest on Kubernetes 1.21.2, that why I encourage you to try the other Kubernetes distros _or_ different Kubernetes versions to...

> Do you know the difference between kubectl apply and create? For the issue cluster, kubectl create works, but kubectl apply will report this error. Ref to https://www.theserverside.com/answer/Kubectl-apply-vs-create-Whats-the-difference If the...