You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Tamir Sagi (Jira)" <ji...@apache.org> on 2023/02/14 15:12:00 UTC

[jira] [Updated] (FLINK-31047) Support topology spread constrains

     [ https://issues.apache.org/jira/browse/FLINK-31047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tamir Sagi updated FLINK-31047:
-------------------------------
    Summary: Support topology spread constrains  (was: Support topology spread constrains when replicas > 1)

> 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
>
> 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)