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

Posted to issues@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2020/01/07 08:40:00 UTC

[jira] [Updated] (FLINK-15483) Starting jobmanager pod should respect environment config option

     [ https://issues.apache.org/jira/browse/FLINK-15483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yang Wang updated FLINK-15483:
------------------------------
    Summary: Starting jobmanager pod should respect environment config option   (was: Support to set environment variables for jobmanager pod)

> Starting jobmanager pod should respect environment config option 
> -----------------------------------------------------------------
>
>                 Key: FLINK-15483
>                 URL: https://issues.apache.org/jira/browse/FLINK-15483
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / Kubernetes
>            Reporter: Yang Wang
>            Priority: Major
>
> Currently, we could use `containerized.master.env.` to set the user-defined environment variables. For Yarn, it works correctly. However, it could not take effect on Kubernetes deployment.
>  
> Some users have tried the flink native integration and find this problem. This is nice to have in 1.10 and not a blocker. Since we could set the environment when building the image instead.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)