[
https://issues.apache.org/jira/browse/FLINK-21383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286253#comment-17286253
]
Yang Wang commented on FLINK-21383:
-----------------------------------
ConfigMap volume is always read-only. So updating the flink-conf.yaml in
JobManager/TaskManager pods will not take effect. We could find the following
error in the console logs.
{code:java}
/docker-entrypoint.sh: line 76: /opt/flink/conf/flink-conf.yaml: Permission
denied
sed: couldn't open temporary file /opt/flink/conf/sedaGciYX: Read-only file
system
/docker-entrypoint.sh: line 76: /opt/flink/conf/flink-conf.yaml: Permission
denied
/docker-entrypoint.sh: line 95: /opt/flink/conf/flink-conf.yaml.tmp: Read-only
file system
{code}
I am not sure whether the users will set the {{FLINK_PROPERTIES}} and
{{JOB_MANAGER_RPC_ADDRESS}} to override the config options in Kubernetes world.
Personally, I prefer to do it via {{-D}} dynamic properties. If we make both
{{jobmanager.sh}} and {{standalone-job.sh}} could support dynamic properties,
then maybe we could give up updating the flink-conf.yaml when it is read-only.
> Docker image does not play well together with ConfigMap based flink-conf.yamls
> ------------------------------------------------------------------------------
>
> Key: FLINK-21383
> URL: https://issues.apache.org/jira/browse/FLINK-21383
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes, flink-docker
> Affects Versions: 1.11.3, 1.12.1, 1.13.0
> Reporter: Till Rohrmann
> Priority: Major
> Labels: usability
>
> Flink's Docker image does not play well together with ConfigMap based
> flink-conf.yamls. The {{docker-entrypoint.sh}} script offers a few env
> variables to overwrite configuration values (e.g. {{FLINK_PROPERTIES}},
> {{JOB_MANAGER_RPC_ADDRESS}}, etc.). The problem is that the entrypoint script
> assumes that it can modify the existing {{flink-conf.yaml}}. This is not the
> case if the {{flink-conf.yaml}} is based on a {{ConfigMap}}.
> Making things worse, failures updating the {{flink-conf.yaml}} are not
> reported. Moreover, the called {{jobmanager.sh}} and {{taskmanager.sh}}
> scripts don't support to pass in dynamic configuration properties into the
> processes.
> I think the problem is that our assumption that we can modify the
> {{flink-conf.yaml}} does not always hold true. If we updated the final
> configuration from within the Flink process (dynamic properties and env
> variables), then this problem could be avoided.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
