[
https://issues.apache.org/jira/browse/FLINK-31047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyula Fora closed FLINK-31047.
------------------------------
Fix Version/s: kubernetes-operator-1.5.0
Assignee: Tamir Sagi
Resolution: Fixed
merged to main 8e1f5cff8d0c5784391245b8818517ec9b8554e7
> Support topology spread constrains
> ----------------------------------
>
> Key: FLINK-31047
> URL: https://issues.apache.org/jira/browse/FLINK-31047
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Tamir Sagi
> Assignee: Tamir Sagi
> Priority: Major
> Labels: flink-kubernetes-operator
> Fix For: kubernetes-operator-1.5.0
>
> Attachments: image-2023-02-15-08-38-49-353.png,
> image-2023-02-15-08-42-04-150.png
>
>
> In case HA is enabled, it should be possible to define topology spread
> constrains to make sure the replicas are deployed on different nodes/zones
> for instance:
> topologySpreadConstraints:
> - maxSkew: 1
> topologyKey: topology.kubernetes.io/zone
> whenUnsatisfiable: DoNotSchedule
> labelSelector :
> matchLabels:
> key: value
> Reference:
> [https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
