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 install fails
See original GitHub issueHi,
We are setupping a new binderhub. We successfully did it last May 2019, but when we tried recently it fails at the helm configuration step :
Error: error installing: the server could not find the requested resource
Following this issue, it seems to be related to helm v2.14.0 and they should fix it in v2.15.0 release, or we can still use kubernetes < v1.16.0
thanks,
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
How to check reason for Helm install failure - Stack Overflow
I wanted to bring up zookeeper using helm install . , but it says Error: release <servicename> failed: services "zookeeper" already exists ....
Read more >Troubleshooting - Helm
helm repo add fails when it used to work In helm 3.3. 1 and before, the command helm repo add <reponame> <url> will...
Read more >Error: INSTALLATION FAILED: failed to download #10285
That error occurs when Helm fails to download the chart from the repository. ... At a high level, helm install looks under your...
Read more >Kubernetes Helm Error: UPGRADE FAILED: another ... - Medium
This error is caused by a helm deployment that never completes successfully. It is likely caused by manually terminating a helm deployment by...
Read more >How to debug helm upgrade failed with message: spec - JFrog
How to debug helm upgrade failed with message: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We’re running Kubernetes v1.13.10-gke.0 for binder.pangeo.io.
There are reported problems with kubespawner (used by binderhub) on k8s 1.16: https://github.com/jupyterhub/kubespawner/issues/354
So even if you fix the helm issue it’s probably safer to use an older k8s for now.