[🚀 Feature]: Topology spread constrains for nodes

[piotrlaczykowski]

Feature and motivation

Hello, Unfortunately, all of our edge nodes go to one k8s worker node. Could you please add topologySpreadConstraints?
Example down below. Right now I am adding it manually to the keda ScaledJob

Usage example

    topologySpreadConstraints:
      - labelSelector:
          matchLabels:
            app: selenium-edge-node
        maxSkew: 4
        topologyKey: kubernetes.io/hostname
        whenUnsatisfiable: DoNotSchedule

[github-actions]

@grubyhs, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[VietND96]

Fixed by 4f2a6e4