cert-manager: Cannot install webhook with helm

I am unable to install due to a validation failure:

missing required field "caBundle" in io.k8s.api.admissionregistration.v1beta1.WebhookClientConfig

The docs say to specify --validate=false, but that is not an option to helm.

I would expect the template to be set up properly to support the k8s v1.12 api since that’s what’s available on EKS.

Environment details:: kubectl client v1.14.1 and server v1.12.6-eks-d69f1b Amazon EKS cluster helm v2.14.0 cert-manager-v0.7.2

/kind bug

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 28 (1 by maintainers)

Most upvoted comments

Hi Team, I am using the lastet version of helm v3.0.0 rc2, I am facing the same issue. But the issue is with kubernetes v 1.12 and caBundle is a required field.

+1 I am also facing the same issue when I try to install vault-helm with 3.x version. Any workaround for current helm version?

Just ran into this and when I went to download the older version of helm I noticed that 2.14.1 has a fix for validation of manifests.

This is fixed in helm now.

Just ran into this and when I went to download the older version of helm I noticed that 2.14.1 has a fix for validation of manifests.

This is fixed in helm now.

thanks for the point

#solution update helm and tiller to 2.14.1 curl https://raw.githubusercontent.com/kubernetes/helm/master/scripts/get > get_helm.sh chmod +x get_helm.sh ./get_helm.sh helm init --service-account tiller helm init --service-account tiller --upgrade helm version helm install --name cert-manager --namespace cert-manager --version v0.8.1 jetstack/cert-manager

Just ran into this and when I went to download the older version of helm I noticed that 2.14.1 has a fix for validation of manifests.

This is fixed in helm now.

I can confirm! Be sure to upgrade tiller also.

In order to extend the Windows answer for bash systems:

Download and make executable (chmod +x) https://raw.githubusercontent.com/helm/helm/master/scripts/get

$ DESIRED_VERSION=v2.13.1 ./helm.sh 
$ helm init --upgrade --force-upgrade

I have the same error on helm 2.14, if i downgrade helm to 2.13 works fine.

This just happened to me after I upgraded to 2.14. @caiohasouza what’s the best way to downgrade?

You could try the following (Windows):

  1. Download version 2.13.0 of helm from releases in the helm GitHub repo.

  2. Check current version:

helm version
Client: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}
  1. Replace helm.exe and tiller.exe with the older versions.

  2. Downgrade helm:

helm init --upgrade
$HELM_HOME has been configured at C:\Users\homer\.helm.
Error: error when upgrading: current Tiller version is newer, use --force-upgrade to downgrade
helm init --upgrade --force-upgrade
$HELM_HOME has been configured at C:\Users\homer\.helm.

Tiller (the Helm server-side component) has been upgraded to the current version.
helm version
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}