[jira] [Created] (FLINK-21383) Docker image does not play well together with ConfigMap based flink-conf.yamls

["Till Rohrmann (Jira)" <ji...@apache.org>]

Till Rohrmann created FLINK-21383:
-------------------------------------

             Summary: 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.12.1, 1.11.3, 1.13.0
            Reporter: Till Rohrmann


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)