Helm - Deployments should support topologySpreadConstraints and priorityClassName

grafana / oncall

Developer-friendly incident response with brilliant Slack integration

GNU Affero General Public License v3.0

3.51k stars 291 forks source link

Helm - Deployments should support topologySpreadConstraints and priorityClassName #2655

Closed njohnstone2 closed 1 year ago

njohnstone2 commented 1 year ago

What would you like to see!

In order to increase availability and prioritise scheduling of oncall pods I would like the ability to configure topologySpreadConstraints and priorityClassName on the celery/engine deployments.

TopologySpreadConstraints are less important for engine as of v1.3.17 the deployment currently only supports a 1:1 mapping with the frontend but it would be useful to have for the celery deployment currently.

Product Area

Helm

Anything else to add?

No response

github-actions[bot] commented 1 year ago

The current version of Grafana OnCall, at the time this issue was opened, is v1.3.17. If your issue pertains to an older version of Grafana OnCall, please be sure to list it in the PR description. Thank you :smile:!