[FLINK-16111] Kubernetes deployment does not respect "taskmanager.cpu.cores".

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.10.0
• Fix Version/s: 1.10.1, 1.11.0
• Component/s: Deployment / Kubernetes
• Labels: pull-request-available
• Assignee: Xintong Song
• Reporter: Xintong Song
• Created: 17/Feb/20 07:32
• Updated: 25/Feb/20 09:07
• Resolved: 25/Feb/20 09:07

Description

The Kubernetes deployment uses `kubernetes.taskmanager.cpu` for configuring TM cpu cores, and will fallback to number-of-slots if not specified.

FLINK-14188 introduced a common option `taskmanager.cpu.cores` (ATM not exposed to users and for internal usage only). A common logic is to decide the TM cpu cores following the fallback order of "common option -> K8s/Yarn/Mesos specific option -> numberOfSlot".

The above fallback rules are not respected by the Kubernetes deployment.

Issue Links

• relates to: FLINK-9953 Active Kubernetes integration
• links to: GitHub Pull Request #11110