[
https://issues.apache.org/jira/browse/FLINK-25765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-25765:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor usability
(was: auto-deprioritized-major stale-minor usability)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> 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.10#820010)
