You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2022/04/26 11:18:00 UTC

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

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

Gyula Fora closed FLINK-27309.
------------------------------
    Resolution: Fixed

Merged to main c377ebe2d31c771576b0bb7345b19db773353a1b

> 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
>            Assignee: Gyula Fora
>            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.7#820007)