You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
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.
The text was updated successfully, but these errors were encountered:
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
dagster/helm/dagster/templates/deployment-celery-queues.yaml
Line 19 in 31f7566
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)
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.
The text was updated successfully, but these errors were encountered: