[jira] [Commented] (FLINK-27309) Allow to load default flink configs in the k8s operator dynamically

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

    [ https://issues.apache.org/jira/browse/FLINK-27309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524240#comment-17524240 ] 

Gyula Fora commented on FLINK-27309:
------------------------------------

+1

I am currently working on FLINK-27023 which will make this simpler. I will open a PR tomorrow and hopefully we can base this work on top of that.

I think the dynamic config should simply rely on watching the configmap containing the default configs for any changes and propagating that to the relevant operator parts.

> Allow to load default flink configs in the k8s operator dynamically
> -------------------------------------------------------------------
>
>                 Key: FLINK-27309
>                 URL: https://issues.apache.org/jira/browse/FLINK-27309
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Biao Geng
>            Priority: Major
>
> Current default configs used by the k8s operator will be saved in the /opt/flink/conf dir in the k8s operator pod and will be loaded only once when the operator is created.
> Since the flink k8s operator could be a long running service and users may want to modify the default configs(e.g the metric reporter sampling interval) for newly created deployments, it may better to load the default configs dynamically(i.e. parsing the latest /opt/flink/conf/flink-conf.yaml) in the {{ReconcilerFactory}} and {{ObserverFactory}}, instead of redeploying the operator.



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