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

Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/01/08 13:23:00 UTC

[jira] [Resolved] (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 ]

Till Rohrmann resolved FLINK-15483.
-----------------------------------
    Resolution: Fixed

Fixed via

master: 9f99d591f88a7ea85346b9b873fac331cdd12ba8
1.10.0: f1ee817b951b5b9140798d23dee9f871711ca0e3

> 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
>    Affects Versions: 1.10.0
>            Reporter: Yang Wang
>            Assignee: Yang Wang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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)