question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Helm 3 fails to install CRDs

See original GitHub issue

Describe the bug If you install the helm chart from the stable repository via helm 3.0.0, the CRDs will not be installed.

To Reproduce

$ helm install ambassador stable/ambassador --namespace ambassador
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
NAME: ambassador
LAST DEPLOYED: Mon Nov 25 11:38:09 2019
NAMESPACE: ambassador
STATUS: deployed
REVISION: 1
NOTES:
Congratulations! You've successfully installed Ambassador.

For help, visit our Slack at https://d6e.co/slack or view the documentation online at https://www.getambassador.io.

To get the IP address of Ambassador, run the following commands:
NOTE: It may take a few minutes for the LoadBalancer IP to be available.
     You can watch the status of by running 'kubectl get svc -w  --namespace ambassador ambassador'

  On GKE/Azure:
  export SERVICE_IP=$(kubectl get svc --namespace ambassador ambassador -o jsonpath='{.status.loadBalancer.ingress[0].ip}')

  On AWS:
  export SERVICE_IP=$(kubectl get svc --namespace ambassador ambassador -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')

  echo http://$SERVICE_IP:
$ helm ls --all-namespaces
NAME            NAMESPACE               REVISION        UPDATED                                 STATUS          CHART                   APP VERSION
ambassador      ambassador              1               2019-11-25 11:38:09.9841677 +0100 CET   deployed        ambassador-4.4.7        0.85.0

No CRDs are registered as the following command does not return anything:

$ kubectl get crd --all-namespaces | grep ambassador

Expected behavior

CRDs should be installed and the following command should show at least a single CRD:

$ kubectl get crd --all-namespaces | grep ambassador
NAME                                                         CREATED AT
something.getambassador.io                                   2019-11-17T13:12:50Z

Versions (please complete the following information):

  • Ambassador (chart: 4.4.7, app version: 0.85.0)
  • Kubernetes environment (Baremetal via Rancher Kubernetes Engine)
  • Version (v1.15.5)

Additional context This bug is tracked in the helm/charts#19008 already, but I wanted to make sure that you guys are aware as the helm chart is currently unusable.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:12 (4 by maintainers)

github_iconTop GitHub Comments

8reactions
dreiccommented, Jan 25, 2020

I can confirm, error is present in helm 3.

4reactions
containerpopecommented, Nov 30, 2019

Helm 3 deprecated the hook for crds and has now a policy that there should be a crd directory

https://v3.helm.sh/docs/topics/charts_hooks/

Read more comments on GitHub >

github_iconTop Results From Across the Web

Custom Resource Definitions - Helm
But CRDs are a modification of the server's behavior. Helm cannot install the CRD on a dry run, so the discovery client will...
Read more >
dask-getway on K8s using helm3: Error: failed to install CRD ...
Posting community wiki answer for better visibility: This is fixed in the repo main. You could grab the CRDs from there, ...
Read more >
Helm3 Kubernetes CRD error on new OpenShift cluster ...
Hi, I got some trouble installing NewRelic on a development Openshift cluster using the kubernetes Helm3 method:
Read more >
Consul helm chart sometimes fails to install CRDs
I noticed that sometimes when I install the consul helm chart it fails to register/install the CRDs. The problem is almost always resolved...
Read more >
Installation fails during common-web-ui chart installation - IBM
The NavConfig CRD was not available when the installation process attempted to install components that depend on the NavConfig CRD. This error is...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found