fresh azure helm deploy stuck on ImagePullBackOff, chartpress did not run?
See original GitHub issueI’ve deployed on an Azure k8 service, ran the helm command as described here:
RELEASE=dask-gateway
NAMESPACE=kube-system
helm upgrade $RELEASE dask-gateway \
--repo=https://helm.dask.org \
--install \
--namespace $NAMESPACE \
--values path/to/your/config.yaml
I’ve changed one line in the recommended config.yaml: password: "sometestingpwd"
.
I’ve also changed the namespace from NAMESPACE=dask-gateway
to NAMESPACE=kube-system
.
The deploy was successful, however the controller-dask-gateway and api-dask-gateway are stuck on status ImagePullBackOff
.
Traefik was able to pull and is happy.
Diving into the .yaml of the two, I found image: ghcr.io/dask/dask-gateway-server:set-by-chartpress
.
Is this the issue, or at least an issue? From what I understand, chartpress was supposed to run as part of the helm chart, is this a misunderstanding? If so, a note in the doc would be helpful. Thanks!
Environment:
- Dask version: 2022.11.0
Issue Analytics
- State:
- Created 9 months ago
- Comments:5
Top Results From Across the Web
tiller pod shows status of ImagePullBackOff in AKS #66 - GitHub
I have created an AKS cluster and been able to do deployments. I planned to use Helm and installed helm locally and initially...
Read more >ImagePullBackOff in AKS - Microsoft Q&A
For each and every image that I try to use in a deployment of my ASK, the ImagePullBackOff error occurs, including for public...
Read more >Kubernetes ImagePullBackOff: Troubleshooting with Examples
Here are some of the possible causes behind your pod getting stuck in the ImagePullBackOff state: Image is not defined properly ...
Read more >ImagePullBackOff error backoff github packages azure aks
I am trying to deploy a Daemonset resource. The container image is hosted on GitHub package registry. The issue is, the nodes that...
Read more >Jupyterhub k8s failing | Error: ImagePullBackOff
Hello Folks, We were able to deploy Jupyterhub on our private shared cluster in GCP using default chart zero-to-jupyterhub-k8s.
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
Ah watch out for the practice of making a copy of the chart’s values.yaml file, provide your own with default values overrides only!
@ZirconCode are you cloning the dask-gateway github repo or similar? There shouldn’t be any reason for you to see set-by-chartpress unless you have cloned the github repo. You are supposed to consume a packaged helm chart directly from helm.dask.org, and not clone the github repository to get the helm chart. If you consume it directly from the github repo you end up with values.yaml having set-by-chartpress entries as well as no values.schema.json file bundled to help you catch config errors etc.
Looking at helm.dask.org’s published helm chart version 2022.11.0, it contains no trace of “set-by-chartpress” or “chartpress” as it shouldn’t after being published there.