You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Boris Lublinsky (Jira)" <ji...@apache.org> on 2020/12/18 03:34:00 UTC
[jira] [Commented] (FLINK-20664) Support setting service account
for TaskManager pod
[ https://issues.apache.org/jira/browse/FLINK-20664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17251475#comment-17251475 ]
Boris Lublinsky commented on FLINK-20664:
-----------------------------------------
Do you mean:
kubernetes.taskmanager.service-account ?
I think a better solution is to use the same service account as job manager. In this case one role and one binding is sufficient. If you make them different, then a user will have to create two bindings
> Support setting service account for TaskManager pod
> ---------------------------------------------------
>
> Key: FLINK-20664
> URL: https://issues.apache.org/jira/browse/FLINK-20664
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Affects Versions: 1.12.0
> Reporter: Yang Wang
> Priority: Critical
> Fix For: 1.12.1
>
>
> 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.jobmanager.service-account}}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)