[
https://issues.apache.org/jira/browse/FLINK-31047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688510#comment-17688510
]
Tamir Sagi edited comment on FLINK-31047 at 2/15/23 6:44 AM:
-------------------------------------------------------------
I added the PR for that ticket along with FLINK-31046
[https://github.com/apache/flink-kubernetes-operator/pull/531]
Tested it locally
3 replicas
!image-2023-02-15-08-38-49-353.png!
The pods have been scheduled on different nodes
!image-2023-02-15-08-42-04-150.png!
was (Author: JIRAUSER283777):
I added the PR for that ticket along with FLINK-31046
https://github.com/apache/flink-kubernetes-operator/pull/531
> 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
> Priority: Major
> Labels: flink-kubernetes-operator
> 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)
