[
https://issues.apache.org/jira/browse/FLINK-26647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532129#comment-17532129
]
Yang Wang commented on FLINK-26647:
-----------------------------------
Actually, I prefer to ship the configuration files via pod template. First,
users need to create a ConfigMap manually, which could be shared by other Flink
clusters. Then mount the ConfigMap via pod template.
> 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)
