[ https://issues.apache.org/jira/browse/FLINK-27650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537734#comment-17537734 ]
Gyula Fora commented on FLINK-27650: ------------------------------------ Thank you [~sparadis] for reporting this, we'll take a look :) > First environment variable of top level pod template is lost > ------------------------------------------------------------ > > Key: FLINK-27650 > URL: https://issues.apache.org/jira/browse/FLINK-27650 > Project: Flink > Issue Type: Bug > Components: Kubernetes Operator > Affects Versions: 1.14.4 > Reporter: Simon Paradis > Priority: Major > Attachments: flink-27650.yaml > > > I am using the Flink operator image *apache/flink-kubernetes-operator:0.1.0* > to deploy Flink 1.14.4 job. The deployment manifest makes use of pod template > feature to inject environment variable to control structured JSON logging. > I noticed the first defined environment variable is never injected into the > JobManager nor TaskManager pods. The work around is to define a dummy env. > var. > Here's the manifest template. This gets processed by a tool that will first > expand ${ENV_VAR} reference with values provided by our CI pipeline. We > should not have to create the FLINK_COORDINATES_DUMMY env var. > > -- This message was sent by Atlassian Jira (v8.20.7#820007)