Unable to deploy via Helm

[jetpacula]

---

name: Bug report
title: Unable to deploy via Helm
labels: bug

---

Describe the bug
Unable to deploy operator via helm.

Environment (please complete the following information):

• Hardware: 3 node cluster Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz RAM 4GB HDD 500GB
• OS: Ubuntu 20.04.3 LTS focal

To Reproduce

$ helm repo add pravega https://charts.pravega.io
$ helm repo update
$ helm install my-book-operator pravega/bookkeeper-operator --set webhookCert.certName=my-selfsigned-ca --set webhookCert.secretName=root-secret

Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1", unable to recognize "": no matches for kind "ValidatingWebhookConfiguration" in version "admissionregistration.k8s.io/v1beta1"]

Expected behavior
Bookkeeper operator in running state

Additional context
CSI used: https://raw.githubusercontent.com/kubernetes-csi/csi-driver-nfs/master/deploy/example/nfs-provisioner/nfs-server.yaml
k8s version: 1.21.1

[anishakj]

@jetpacula have you installed cert-manager and secrets before installing the operator? Please refer https://github.com/pravega/charts/tree/master/charts/bookkeeper-operator#prerequisites

[jetpacula]

@anishakj yes, as you can see I used them during deployment, which I stated in the "To Reproduce" section
helm install my-book-operator pravega/bookkeeper-operator --set webhookCert.certName=my-selfsigned-ca --set webhookCert.secretName=root-secret

[anishakj]

@jetpacula then probably it might be due to v1beta1 is not supported in k8 version 1.21.1

[jetpacula]

@anishakj which exact k8s version is compatible? The deployment guide says its 1.16+ which includes 1.21.1

[anishakj]

@jetpacula Bookkeeper-operator is updated to use v1 CRD and webhook configuration. Could you please try with that update

[anishakj]

@jetpacula Bookkeeper-operator is updated to use v1 CRD and webhook configuration. Could you please try with that update

Is the new version solving your issue?