[FLINK-20664] Support setting service account for TaskManager pod

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.12.0
• Fix Version/s: 1.12.1, 1.13.0
• Component/s: Deployment / Kubernetes
• Labels: pull-request-available
• Assignee: Boris Lublinsky
• Reporter: Yang Wang
• Created: 18/Dec/20 02:42
• Updated: 25/Dec/20 09:05
• Resolved: 25/Dec/20 09:05

Description

Currently, we only set the service account for JobManager. The TaskManager is using the default service account. Before the KubernetesHAService is introduced, it works because the TaskManager does not need to access the K8s resource(e.g. ConfigMap) directly. But now the TaskManager needs to watch ConfigMap and retrieve leader address. So if the default service account does not have enough permission, users could not specify a valid service account for TaskManager.

 

We should introduce a new config option for TaskManager service account. 

kubernetes.taskmanager.service-account

 

 

Issue Links

• links to: GitHub Pull Request #14439
• links to: GitHub Pull Request #14447