You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2020/03/24 10:50:00 UTC

[jira] [Created] (FLINK-16749) Support to set node selector for JM/TM pod

Yang Wang created FLINK-16749:
---------------------------------

             Summary: Support to set node selector for JM/TM pod 
                 Key: FLINK-16749
                 URL: https://issues.apache.org/jira/browse/FLINK-16749
             Project: Flink
          Issue Type: Sub-task
          Components: Deployment / Kubernetes
            Reporter: Yang Wang
             Fix For: 1.11.0


The [node-selector|https://kubernetes.io/docs/concepts/configuration/assign-pod-node/] is a collection of key/value pairs to constrain a pod to only be able to run on particular node(s). Since affinity and anti-affinity are uncommon use case for Flink, so we leave the support in pod template.

 
{code:java}
public static final ConfigOption<Map<String, String>> JOB_MANAGER_NODE_SELECTOR =
 key("kubernetes.jobmanager.node-selector")
 .mapType()
 .noDefaultValue()
 .withDescription("The node selector to be set for JobManager pod. Specified as key:value pairs separated by " +
  "commas. For example, environment:production,disk:ssd.");

public static final ConfigOption<Map<String, String>> TASK_MANAGER_NODE_SELECTOR =
 key("kubernetes.taskmanager.node-selector")
 .mapType()
 .noDefaultValue()
 .withDescription("The node selector to be set for TaskManager pods. Specified as key:value pairs separated by " +
  "commas. For example, environment:production,disk:ssd.");
{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)