[ https://issues.apache.org/jira/browse/FLINK-34565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831336#comment-17831336 ]
Zhu Zhu commented on FLINK-34565: --------------------------------- IIUC, the requirement is to ship more user files, which may be needed by user code, to the pod. Supporting configuration files is just a special case of it. Shipping them via ConfigMap sounds a bit tricky to me. cc [~wangyang0918] > Enhance flink kubernetes configMap to accommodate additional configuration > files > -------------------------------------------------------------------------------- > > Key: FLINK-34565 > URL: https://issues.apache.org/jira/browse/FLINK-34565 > Project: Flink > Issue Type: Bug > Components: Deployment / Kubernetes > Reporter: Surendra Singh Lilhore > Priority: Major > Labels: pull-request-available > > Flink kubernetes client currently supports a fixed number of files > (flink-conf.yaml, logback-console.xml, log4j-console.properties) in the JM > and TM Pod ConfigMap. In certain scenarios, particularly in app mode, > additional configuration files are required for jobs to run successfully. > Presently, users must resort to workarounds to include dynamic configuration > files in the JM and TM. This proposed improvement allows users to easily add > extra files by configuring the > '{*}kubernetes.flink.configmap.additional.resources{*}' property. Users can > provide a semicolon-separated list of local files in the client Flink config > directory that should be included in the Flink ConfigMap. -- This message was sent by Atlassian Jira (v8.20.10#820010)