[ 
https://issues.apache.org/jira/browse/FLINK-20324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238489#comment-17238489
 ] 

Boris Lublinsky commented on FLINK-20324:
-----------------------------------------

Thank you Yang Wang

Env variables is new in 1.12, I did not notice it - my bad

Secrets mounting is also new in 1.12 and is exactly the same as I have done

Volume/Config mount is quite similar to what I have implemented and I can 
easily extend it to do the same

Owner reference is still missing.

We are targeting 1.12 for this, so lets discuss what we can add easily and I 
can rework PR quickly

 

> Support  customizing of containers for native kubernetes setup
> --------------------------------------------------------------
>
>                 Key: FLINK-20324
>                 URL: https://issues.apache.org/jira/browse/FLINK-20324
>             Project: Flink
>          Issue Type: New Feature
>          Components: Deployment / Kubernetes
>    Affects Versions: 1.11.2
>         Environment: Kubernetes
>            Reporter: Boris Lublinsky
>            Priority: Major
>             Fix For: 1.12.0, 1.11.2
>
>   Original Estimate: 12h
>  Remaining Estimate: 12h
>
> A common requirement for Flink applications is usage of custom resources 
> (Environment variables, PVCs, Secrets, configMaps, etc). For example, usage 
> of NFS-based checkpointing, require mounting NFS volumes, access to databases 
> might require environment variables and secrets, the ability to safely remove 
> cluster manager deployment might require owner's reference, etc.
> All of these resources can be added to created pods using Pod decorators 
> already defined by Flink. So implementation of such support is as simple as 
> implementing of new decorators and wiring them correctly to the appropriate 
> factories.
>  
> An implementation of such support is provided in this pull request 
> [https://github.com/apache/flink/pull/14005]



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

Reply via email to