Skip to content

Commit

Permalink
[FLINK-20664][k8s][doc] Update RBAC section in native kubernetes docu…
Browse files Browse the repository at this point in the history
…ment

This closes apache#14447
  • Loading branch information
wangyang0918 authored and xintongsong committed Dec 25, 2020
1 parent fb4286f commit 4e5448c
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 2 deletions.
3 changes: 2 additions & 1 deletion docs/deployment/resource-providers/native_kubernetes.md
Original file line number Diff line number Diff line change
Expand Up @@ -307,7 +307,8 @@ $ kubectl create clusterrolebinding flink-role-binding-default --clusterrole=edi
{% endhighlight %}

If you do not want to use the `default` service account, use the following command to create a new `flink-service-account` service account and set the role binding.
Then use the config option `-Dkubernetes.jobmanager.service-account=flink-service-account` to make the JobManager pod use the `flink-service-account` service account to create and delete TaskManager pods.
Then use the config option `-Dkubernetes.service-account=flink-service-account` to make the JobManager pod use the `flink-service-account` service account to create/delete TaskManager pods and leader ConfigMaps.
Also this will allow the TaskManager to watch leader ConfigMaps to retrieve the address of JobManager and ResourceManager.

{% highlight bash %}
$ kubectl create serviceaccount flink-service-account
Expand Down
3 changes: 2 additions & 1 deletion docs/deployment/resource-providers/native_kubernetes.zh.md
Original file line number Diff line number Diff line change
Expand Up @@ -307,7 +307,8 @@ $ kubectl create clusterrolebinding flink-role-binding-default --clusterrole=edi
{% endhighlight %}

If you do not want to use the `default` service account, use the following command to create a new `flink-service-account` service account and set the role binding.
Then use the config option `-Dkubernetes.jobmanager.service-account=flink-service-account` to make the JobManager pod use the `flink-service-account` service account to create and delete TaskManager pods.
Then use the config option `-Dkubernetes.service-account=flink-service-account` to make the JobManager pod use the `flink-service-account` service account to create/delete TaskManager pods and leader ConfigMaps.
Also this will allow the TaskManager to watch leader ConfigMaps to retrieve the address of JobManager and ResourceManager.

{% highlight bash %}
$ kubectl create serviceaccount flink-service-account
Expand Down

0 comments on commit 4e5448c

Please sign in to comment.