[
https://issues.apache.org/jira/browse/FLINK-25765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480929#comment-17480929
]
Chesnay Schepler commented on FLINK-25765:
------------------------------------------
??manage user's expectations regarding the configmap??
I'd rather do this. As is we expect users to set the configmap once and to then
never touch it again.
> Kubernetes: flink's configmap and flink's actual config are out of sync
> -----------------------------------------------------------------------
>
> Key: FLINK-25765
> URL: https://issues.apache.org/jira/browse/FLINK-25765
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Affects Versions: 1.15.0
> Reporter: Niklas Semmler
> Priority: Major
> Labels: usability
>
> For kubernetes setups, Flink's configmap does not reflect the actual config.
> Causes
> # Config values are overridden by the environment variables in the docker
> image (see FLINK-25764)
> # Flink reads the config on start-up, but does not subscribe to changes
> # Changes to the config map do not lead to restarts of the flink cluster
> Effects
> # Users cannot expect to understand Flink's config from the configmap
> # TaskManager/JobManager started at different times may start with different
> configs, if the user edits the configmap
> Related to FLINK-21383.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
