fix(helm): Set priorityClassName to pods (superset, celeryBeat, celeryBeatFlower, celeryBeatWorker, celeryBeatWebsocket, jobs)

[sabyrzhan]

SUMMARY

Add ability to assign custom priorityClassName to pods. Each workload (superset, celeryBeat, celeryBeatFlower, celeryBeatWorker, celeryBeatWebsocket, jobs) has ability to assign custom priorityClassName

TESTING INSTRUCTIONS

Specify custom priorityClassName to one of the deployments (superset, celeryBeat, celeryBeatFlower, celeryBeatWorker, celeryBeatWebsocket, jobs) to assign to its pods

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[github-actions]

Congrats on making your first PR and thank you for contributing to Superset! 🎉 ❤️

We hope to see you in our Slack community too! Not signed up? Use our Slack App to self-register.

[craig-rueda]

Can you please bump the chart version and re-build the chart README?

[sabyrzhan]

@craig-rueda Yes, I can. But isnt it done automatically after the merge? Or should I trigger manually a workflow? Could you just elaborate a little about the process please?

[sabyrzhan]

Ok, I see it needs to be released locally if I am not wrong, and send as a separate PR like this, is that right?
#27946

[villebro]

LGTM (I've also needed this, so I assume this is useful to the general public, too). Not sure what the unrelated lint issue is, will try to repro locally.

[sabyrzhan]

@villebro Thank you for review. I wrote yesterday in slack channel. Maybe you missed it.
The related MR that broke it is this: #28762 from @hanslemm.
Seems like linting skipped on it: https://github.com/apache/superset/actions/runs/9381289976

[villebro]

@villebro Thank you for review. I wrote yesterday in slack channel. Maybe you missed it. The related MR that broke it is this: #28762 from @hanslemm. Seems like linting skipped on it: https://github.com/apache/superset/actions/runs/9381289976

@sabyrzhan oh, that skip on CI shouldn't have happened IMO (probably warrants looking into separately from this, though) 🙁 Do you think you'll be able to fix it as a bycatch here? I'm assuming it should be simple to fix. If not I can take a stab at it.

[sabyrzhan]

@villebro sure, not a problem. Will start fixing right now and push it.

[villebro]

Thanks @sabyrzhan !

[sabyrzhan]

@villebro Pushed the fix.

[villebro]

Restamping - big thanks for fixing this unrelated error!

[sabyrzhan]

@villebro Any estimates when the next release of the helm chart is going to be? I see the last one was on May.

[villebro]

@sabyrzhan the helm chart should be automatically released by CI. Let me take a look to see why this is not the case..

[akerkau]

@villebro It seems as if this feature is still not available in the latest chart. Can you have another look?

[villebro]

I'm now investigating why the GHA workflow isn't triggering.

[villebro]

@akerkau please help by reviewing the following fix PR: #30924

[akerkau]

@villebro Thanks for the fix. Happy about the working priorityClassName feature.