[jira] [Resolved] (FLINK-26875) Operator Helm: Extends the rbac options with separate namespaces param

["Xin Hao (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-26875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xin Hao resolved FLINK-26875.
-----------------------------
    Resolution: Not A Problem

> Operator Helm: Extends the rbac options with separate namespaces param
> ----------------------------------------------------------------------
>
>                 Key: FLINK-26875
>                 URL: https://issues.apache.org/jira/browse/FLINK-26875
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Xin Hao
>            Priority: Minor
>
> Currently, the Flink Kubernetes Operator Helm Chart uses the *watchNamespaces* to determine which namespaces should the roles be created.
> {code:java}
> {{- if .Values.rbac.create }}
> {{- if .Values.watchNamespaces }}
> {{- range .Values.watchNamespaces }}
>   ...{code}
> But my use case is that I have another operator for myself to observe the Flink Operator's CRs so that I want to create roles in more namespaces.
> So the requirement for me is that add another param called namespaces under the *rbac* section and *defaults to watchNamespaces.* 
> It will look like this:
> {code:java}
> # values.yaml
> rbac:
>   create: true
>   # The namespaces should create the roles, defaults to watchNamespaces
>   # namespaces: ["flink"]
> # rbac.yaml
> {{- if or .Values.rbac.namespaces .Values.watchNamespaces }}
> {{- range (default .Values.watchNamespaces .Values.rbac.namespaces) }}{code}
> So that the users can create their role bindings.
> The reason that the users shouldn't create roles by themselves is the contents of the role should be managed y the Flink Helm chart.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)