[jira] [Commented] (FLINK-15656) Support user-specified pod templates

["Yang Wang (Jira)" <ji...@apache.org>]

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

Yang Wang commented on FLINK-15656:
-----------------------------------

[~felixzheng] Thanks a lot for working on this. Recently, i am also thinking about which feature should be supported in flink configuration directly. And i have asked some suggestion from our users. I get the very rough conclusion here.

> Very common use features. They should be directly supported in flink configuration
 * Kube config, namespace, service account, image(pull-policy, secrets), service exposed type
 * Annotations, Labels, NodeSelector
 * Toleration
 * Mem and cpu resources for jobmanager and taskmanager
 * Jobmanager deployment replication, support multiple jobmanagers to get fast recovery

> Uncommon, but required by few production users. Maybe pod template is enough.
 * Affinity and anti-affinity
 * Volume mount, from persistent volume, user created configmap, etc.
 * Dns policy
 * Sidecar container, will be used for debugging, log collecting, etc. In our internal production environment, we choose log4j2 custom appender to collect the jobmanager/taskmanger logs to persistent storage(HDFS, Aliyun OSS, etc.)
 * Init container, various initialization before user program running, download user jars and dependencies, register with external system, etc. In our deployer platform, we provide two ways for the image choice, user specified image with users jars baked in or official image with init container.

 

[~felixzheng] [~ouyangwuli] Please correct me if i am wrong. Also feel free to share your thoughts about this.

> Support user-specified pod templates
> ------------------------------------
>
>                 Key: FLINK-15656
>                 URL: https://issues.apache.org/jira/browse/FLINK-15656
>             Project: Flink
>          Issue Type: New Feature
>          Components: Deployment / Kubernetes
>            Reporter: Canbin Zheng
>            Priority: Major
>
> The current approach of introducing new configuration options for each aspect of pod specification a user might wish is becoming unwieldy, we have to maintain more and more Flink side Kubernetes configuration options and users have to learn the gap between the declarative model used by Kubernetes and the configuration model used by Flink. It's a great improvement to allow users to specify pod templates as central places for all customization needs for the jobmanager and taskmanager pods.



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