[jira] [Updated] (FLINK-26574) Allow definining Operator configuration in Helm chart Values

["Gyula Fora (Jira)" <ji...@apache.org>]

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

Gyula Fora updated FLINK-26574:
-------------------------------
    Description: 
Currently the Helm chart hardodes the flink-operator-config and flink-default-config configmap that contains the configurations (logging and yaml).

We should allow the users to define the contents of these config files directly in the helm Values yaml.

Also we should probably rename the flink-conf.yaml config key to operator-conf.yaml in flink-operator-config to not confuse it with flink accidentally.

  was:
Currently the Helm chart hardodes the flink-operator-config configmap that contains the operator configurations (logging and yaml).

We should allow the users to define the contents of these config files directly in the helm Values yaml.

Also we should probably rename the flink-conf.yaml config key to operator-conf.yaml to not confuse it with flink accidentally.


> Allow definining Operator configuration in Helm chart Values
> ------------------------------------------------------------
>
>                 Key: FLINK-26574
>                 URL: https://issues.apache.org/jira/browse/FLINK-26574
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Priority: Major
>
> Currently the Helm chart hardodes the flink-operator-config and flink-default-config configmap that contains the configurations (logging and yaml).
> We should allow the users to define the contents of these config files directly in the helm Values yaml.
> Also we should probably rename the flink-conf.yaml config key to operator-conf.yaml in flink-operator-config to not confuse it with flink accidentally.



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