[jira] [Commented] (FLINK-34565) Enhance flink kubernetes configMap to accommodate additional configuration files

["Surendra Singh Lilhore (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-34565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17833440#comment-17833440 ] 

Surendra Singh Lilhore commented on FLINK-34565:
------------------------------------------------

[~zhuzh] If the user files are dynamic, then it is very useful to support them in ConfigMap, especially in an App Mode cluster.

 A similar use case was discussed on the user mailing list: [link to the mailing list thread.|https://lists.apache.org/thread/md2zq0dbvt2dxytdfxw16jbfh02yq0w9]

> 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)