[
https://issues.apache.org/jira/browse/FLINK-33633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795452#comment-17795452
]
Ryan van Huuksloot commented on FLINK-33633:
--------------------------------------------
Would there be any appetite to have the operator create just a ClusterRole for
Flink?
We can then leave the RoleBinding to the specific deployment to not scope
creep. It at least removes one extra resource per deployment. I think this
would be safe.
> Automatic creation of RBAC for instances of Flink Deployments
> -------------------------------------------------------------
>
> Key: FLINK-33633
> URL: https://issues.apache.org/jira/browse/FLINK-33633
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.7.0
> Reporter: Tony Garrard
> Priority: Not a Priority
>
> Currently users have to manually create RBAC e.g. the flink service account.
> When operator is watching all namespaces; creation of a FlinkDeployment in a
> specific namespace may fail if the kube admin has failed to create the
> required RBAC. To improve usability the operator could be coded to
> automatically create these rbac resources in the instance namespace if not
> present
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
