[
https://issues.apache.org/jira/browse/FLINK-27309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524250#comment-17524250
]
Aitozi commented on FLINK-27309:
--------------------------------
I think it's a very useful feature in production. But do we need to outline
what config can dynamically take effect. Currently, most option are controlling
the reconciler interval or check behavior can take effect at the next reconcile
turn. But still with option like {{operator.reconciler.max.parallelism}} which
may can't take effect directly, Right ?
> 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)
