[FLINK-16749] Support to set node selector for JM/TM pod

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.11.0
• Component/s: Deployment / Kubernetes
• Labels: pull-request-available
• Assignee: Yang Wang
• Reporter: Yang Wang
• Created: 24/Mar/20 10:49
• Updated: 07/Apr/20 08:06
• Resolved: 07/Apr/20 08:06

Description

The node-selector 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.

 

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.");

Issue Links

• links to: GitHub Pull Request #11500