[
https://issues.apache.org/jira/browse/FLINK-27309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525012#comment-17525012
]
Biao Geng commented on FLINK-27309:
-----------------------------------
Thanks [~gyfora]! Besides [~aitozi]'s valuable point, I also think about if the
changed default configs should take effect for a running job deployment.
>From k8s side, it may make sense that such change should be considered as
>`specChanged`, and all the running job will be suspended and restarted.
I am not sure it is proper to restart running jobs(i.e. changed default configs
affect running jobs) from Flink users' side.
> 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)
