[
https://issues.apache.org/jira/browse/FLINK-25765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-25765:
-----------------------------------
Labels: stale-major usability (was: usability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: stale-major, 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)
