You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Surendra Singh Lilhore (Jira)" <ji...@apache.org> on 2024/03/02 06:29:00 UTC

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

Surendra Singh Lilhore created FLINK-34565:
----------------------------------------------

             Summary: 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


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)