-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can´t create Dask Cluster on GKE using Artifact Registry #341
Comments
I'm sorry you're having trouble here. I don't have any experience deploying with a custom registry, perhaps @droctothorpe has some thoughts? Dask-Gateway is pretty quick about deleting failed pods (we should probably add a config option to delay this to help with debugging). If you start a watch for pods in the namespace you might catch something. Something like this might work:
I'd look for pods getting created, then check the
Pods are created by the dask-gateway controller, the RBAC entry is created here: https://github.com/dask/dask-gateway/blob/master/resources/helm/dask-gateway/templates/controller/rbac.yaml. |
We have been using Artifactory to store and retrieve images without issue. The gateway:
replicas: 2
resources:
limits:
cpu: 100m
memory: 256Mi
requests:
cpu: 100m
memory: 256Mi
loglevel: DEBUG
image:
name: <internal-artifactory-url>/dask-gateway-server
tag: <tag>
pullPolicy: Always
podDisruptionBudget:
minAvailable: 1
...
backend:
image:
name: <internal-artifactory-url>/dask-gateway-worker
tag: <tag>
pullPolicy: Always
namespace: <namespace> Are you passing in the image tag? Have you enabled debug logs? I recommend doing so and monitoring logs from the API and controller. You can do so individually with |
What happened:
I am deploying Dask Gateway on a GKE cluster using the helm chart.
I have setup a custom image that is stored in Artifact Registry for the Schedulers and workers. I have used for that purpose the key
gateway.backend.image.name
ofvalues.yam
with an example valueeurope-west6-docker.pkg.dev/project1/images/dask
.When I try to create a cluster with:
Please, take in mind that I am using
localhost
as I made a port-forwad to the podtraefik-dask-gateway
.The code throws me the next error:
I can´t find any logs with a more detailed error.
The fact is that If I store that image in other Docker image repositories it is working.
What Kubernetes Service Account is using Dask Gateway for pulling the images? I don´t see any pod getting launched even with a
PullImageError
or a similar error.What you expected to happen:
I would expect the cluster to be created like with images stored in other repositories.
# Put your MCVE code here
Anything else we need to know?:
Environment:
The text was updated successfully, but these errors were encountered: