[jira] [Commented] (FLINK-25765) Kubernetes: flink's configmap and flink's actual config are out of sync

["Niklas Semmler (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-25765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480695#comment-17480695 ] 

Niklas Semmler commented on FLINK-25765:
----------------------------------------

I think we have to either manage user's expectations regarding the configmap or put configmap and flink's actual config into sync.

If we go for the latter:

For causes 2 and 3, I see two remedies. Either, Flink restarts with every change to the configmap or we set the configmap to immutable [1]. The first option could lead to accidental restarts, so I'd go with the second option.

For cause 1, maybe it is a good solution to ignore environment variables in the Kubernetes context? (In contrast to a docker context.) To me, it seems more plausible to have a single place to edit the config.

[1] https://kubernetes.io/docs/concepts/configuration/configmap/#configmap-immutable

> 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



--
This message was sent by Atlassian Jira
(v8.20.1#820001)