velero helm install fails

[thulasidassrinivasan]

I am trying to install velero using helm in azure kubernetes service and i get below error message.
Error: failed post-install: unable to build kubernetes object for deleting hook velero/templates/backupStorageLocation.yml: unable to recognize "": no matches for kind "BackupStorageLocation" in version "velero.io/v1"

command used to install
helm install --generate-name --namespace velero -f charts/values-uat.yaml --set global.env=uat --set global.col=green charts/

Running velero backup-location get and velero snapshot-location get throws
An error occurred: the server could not find the requested resource (get backupstoragelocations.velero.io)
An error occurred: the server could not find the requested resource (get volumesnapshotlocations.velero.io)

velero version i am using is v1.3.2 and plugin version is velero/velero-plugin-for-microsoft-azure:v1.0.1. How to fix this ?

kubernetes version : 1.19.7

[zubron]

Hi @thulasidassrinivasan. This sounds like the CRDs for Velero have not been installed. Can you run kubectl get crds and verify that the output contains a number of CRDs with velero.io in the name?

I'm not an expert on Helm, but I wonder if the CRDs are not being installed due to the command you are using. Are there any other charts under your charts/ directory? Please review our documentation on how to install the Helm chart as there are some differences that may impact how the resulting chart is installed: https://github.com/vmware-tanzu/helm-charts/tree/main/charts/velero#installing-the-velero-server

Thanks!

[jenting]

No worries, this is because the API version apiextensions.k8s.io/v1beta1 is deprecated and will be unavailable in v1.22+.

[thulasidassrinivasan]

Thanks but I could see all crd's are still using apiextensions.k8s.io/v1beta1 even if it install it via velero cli. When it is planned to be changed ?

[jenting]

Velero has to cover multiple K8s version >= 1.12, this means that Velero needs to support both apiextensions.k8s.io/v1beta1 and apiextensions.k8s.io/v1 simultaneously. Furthermore, since Velero supports displaying CRDs only (velero install --crds-only --dry-run -o yaml), we don't know which K8s version the user is using now.
It's not an intuition just bump the version from v1beta to v1.

#2505 (comment)

[jenting]

@thulasidassrinivasan Is the issue be solved?

[thulasidassrinivasan]

@jenting - Yeah. Thanks for the answers.