You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Diego Lobba (Jira)" <ji...@apache.org> on 2025/03/12 14:40:00 UTC

[jira] [Created] (FLINK-37467) FlinkSessionJob: possibility to use configmaps and secrets in args parameter

Diego Lobba created FLINK-37467:
-----------------------------------

             Summary: FlinkSessionJob: possibility to use configmaps and secrets in args parameter
                 Key: FLINK-37467
                 URL: https://issues.apache.org/jira/browse/FLINK-37467
             Project: Flink
          Issue Type: Improvement
          Components: Kubernetes Operator
    Affects Versions: 1.10.0
            Reporter: Diego Lobba


It would be nice to have the args parameter used by the Flink job as a string interpolated using existing Kubernetes configmap and secrets resources.

Pros:
 * using kubernetes native resources to manage secrets and configuration values
 * avoid duplicating configurations used by multiple jobs
 * tracking of dependant configmaps and secrets used by the FlinkSessionJob

Considerations:
 * The pod runningĀ  the job has access to all environment variables defined in the target session cluster, however
 * the args parameter does not enable interpolating environment variables, for instance if string "${MY_ENV_VARIABLE}" is defined as string value to the args parameter, there is no interpolation and the job is going to see the literal string value passed; moreover
 * increasing the number of environment variables to the session cluster does not scale well with the number of jobs, is not enforcing job independence as a principle and would required downtime to all job managed by the session cluster in case any of them require an update to the environment variable.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)