[
https://issues.apache.org/jira/browse/FLINK-26647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531498#comment-17531498
]
Aitozi commented on FLINK-26647:
--------------------------------
I think it will bring convenience to add a way to add config files to the
configMap. Because we can not predict what config files users may need.
Meanwhile, users are responsible for the files to be shipped, they should pay
attention to avoid to add too much files to the configMap. If it's necessary to
guard the shipped config files not too large, we can check the size before
create the configMap, Right? But I have not come up with a suitable size
threshold.
I lean to make it easy to ship config files first, and add the safe guard if
necessary, what do you think [~wangyang0918] ?
> Can not add extra config files on native Kubernetes
> ----------------------------------------------------
>
> Key: FLINK-26647
> URL: https://issues.apache.org/jira/browse/FLINK-26647
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Affects Versions: 1.13.5
> Reporter: Zhe Wang
> Priority: Critical
>
> When using native Kubernetes mode (both session and application), predefine
> FLINK_CONF_DIR environment with config files in. Only two files(
> *flink-conf.yaml and log4j-console.properties* ) are populated to configmap
> which means missing of other config files(like sql-client-defaults.yaml,
> zoo.cfg etc.)
> Tried these, neither worked out:
> 1) After native Kubernetes startup, change both configmap and deployment:
> 1. add all my config files to configmap.
> 2. add config file to deployment.spec.template.spec.volumes[]
> 3. Flink job pod startups fail(log: lost leadership )
>
> 2) Using a *pod-template-file.taskmanager* file:
> 1. add config files to created confimap.
> 2. add my config files to template(others can be merged by Flink as guide
> says)
> 3. Flink task pod startup fail, log: Duplicated volume name
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
