[
https://issues.apache.org/jira/browse/FLINK-17077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17109795#comment-17109795
]
Eui Heo commented on FLINK-17077:
---------------------------------
Thanks for your review.
The original motivation of this issue is related to mounting flink-conf.yaml as
kubernetes configMap. [issue
link|https://github.com/GoogleCloudPlatform/flink-on-k8s-operator/issues/213]
I want to provide two options to users.
1) Default option: Keep flink-conf.yaml declaratively via configMap
In the case of which user want to manage the configuration by configMap only.
Basically workloads on k8s are managed with declarative resources, so I think
this option as default.
2) Support to change flink properties with k8s downward API on runtime via
docker-entrypoint script.
For the second option, I considered copying flink-conf.yaml to another path and
changing FLINK_CONF_DIR to locate the configuration location because mounted
flink-conf.yaml is read-only.
Could you consider this use case?
> FLINK_CONF_DIR environment variable to locate flink-conf.yaml in Docker
> container
> ---------------------------------------------------------------------------------
>
> Key: FLINK-17077
> URL: https://issues.apache.org/jira/browse/FLINK-17077
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Docker
> Reporter: Eui Heo
> Assignee: Eui Heo
> Priority: Major
> Labels: Kubernetes, docker
>
> To use flink-conf.yaml outside Flink home directory, we should use
> FLINK_CONF_DIR.
> But despite of FLINK_CONF_DIR is provided, docker-entrypoint.sh in official
> flink-docker doesn't know FLINK_CONF_DIR and it is ignored when append
> additional flink properties to flink-conf.yaml. It would be good to use
> FLINK_CONF_DIR for the location of flink-conf.yaml, if user provide it.
> https://github.com/apache/flink-docker/blob/master/docker-entrypoint.sh#L23
--
This message was sent by Atlassian Jira
(v8.3.4#803005)