Skip to content
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

Dagster helm: unable to configure autoscaling for celery workers due to broad deployment selectors. #25950

Open
msavtchouk-pf opened this issue Nov 15, 2024 · 0 comments
Labels
deployment: k8s Related to deploying Dagster to Kubernetes type: bug Something isn't working

Comments

@msavtchouk-pf
Copy link

What's the issue?

I am trying to configure HPA for my celery workers
https://cloud.google.com/kubernetes-engine/docs/concepts/horizontalpodautoscaler

Due to selector annotation on deployment-celery-queues

Google Cloud k8s cluster assumes that all pods are managed by this deployment and thus fails to apply auto-scaling (resources must be specified on each of the pods)
image
When I patched the deployment so that it only includes the celery pods, the autoscaling worked.

What did you expect to happen?

I expected that I can specify deployment labels (or they are automatically specified) for celery queues in my helm chart.

How to reproduce?

No response

Dagster version

1.8.13

Deployment type

Dagster Helm chart

Deployment details

Deploying on GKE

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
By submitting this issue, you agree to follow Dagster's Code of Conduct.

@msavtchouk-pf msavtchouk-pf added the type: bug Something isn't working label Nov 15, 2024
@garethbrickman garethbrickman added the deployment: k8s Related to deploying Dagster to Kubernetes label Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployment: k8s Related to deploying Dagster to Kubernetes type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants