Add topologySpreadConstraints for workers

[tadeha]

This PR adds support for topologySpreadConstraints to the worker deployment. This allows users to improve cluster resilience and resource balancing by controlling how worker pods are spread across nodes and availability zones.

The feature is enabled by setting the worker.topologySpreadConstraints value in values.yaml. Tests have been added to verify the implementation.

Example values.yaml configuration:

worker:
  topologySpreadConstraints:
    - maxSkew: 1
      topologyKey: "kubernetes.io/hostname"
      whenUnsatisfiable: "ScheduleAnyway"
      labelSelector:
        matchLabels:
          app.kubernetes.io/name: trino
          app.kubernetes.io/component: worker

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[cla-bot]

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

[nineinchnick]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[akkbng]

Hey @tadeha , thanks for adding this!
quick question: are you also planning on adding the topologySpreadConstraints support for the coordinator deployment?

[tadeha]

deployment

Hi @akkbng, actually, having multiple coordinators didn't make sense to us, so we stick to workers for now. You can add them with the same template.