[FLINK-24150] Support to configure cpu resource request and limit in pod template

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Deployment / Kubernetes
• Labels: pull-request-available
• Assignee: Unassigned
• Reporter: Yang Wang
• Created: 03/Sep/21 12:00
• Updated: 07/Dec/23 05:54

Description

Why Flink needs to overwrite memory resource defined in pod template?
The major reason is that Flink need to ensure the consistency between Flink configuration
(taskmanager.memory.process.size , kubernetes.taskmanager.cpu) and pod template resource settings. Since users could specify the total process memory or detailed memory[2], Flink will calculate the pod resource internally.
 
For the CPU case the template’s requests/limits should have priority if they are specified. The factor could still be used if the template doesn’t specify anything. The logic could be something like this:

1. To choose CPU request
2. Read pod template first
3. If template doesn’t have anything, read from kubernetes.taskmanager.cpu
4. If configuration is not specified, fall back to default

1. To choose CPU limit
2. Read from template first
3. If template doesn’t have anything, apply factor to what was chosen in step 1, where the default factor is 1.

Issue Links

• is related to: FLINK-15648 Support to configure limit for CPU and memory requirement
• links to: GitHub Pull Request #23872