[FLINK-14460] Active Kubernetes integration phase 2 - Advanced Features

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.11.0
• Component/s: Deployment / Kubernetes
• Assignee: Unassigned
• Reporter: Yang Wang
• Created: 19/Oct/19 11:04
• Updated: 01/Oct/20 00:56
• Resolved: 18/May/20 11:28

Description

This is phase 2 of active kubernetes integration. It is a umbrella jira to track all the advanced features and make Flink on Kubernetes production ready.

 

Since the K8s is fast evolving and many new features will be supported in the future. Recently, i am 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 FLINK-15656 is enough(will be supported in phase3).

• 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. We provide two ways for the image choice, user specified image with users jars baked in or official image with init container.

Issue Links

• is related to: FLINK-9953 Active Kubernetes integration
• is related to: FLINK-17709 Active Kubernetes integration phase 3 - Advanced Features
• links to: Kubernetes native integration implementation

Sub-Tasks

• Support application mode in kubernetes: Closed
• Support to ship user config files on kubernetes: Closed
• Support to set toleration for jobmanager and taskmanger: Closed
• Support to set user specified labels for JM/TM pod: Closed
• Support to set node selector for JM/TM pod: Closed
• Support for imagePullSecrets k8s option: Closed
• Support user-specified annotations for JM/TM pods: Resolved
• Rethink the necessity of the internal Service: Closed
• Support to mount Hadoop Configurations: Closed
• Configurable K8s context support: Closed
• Rework the Service design for native Kubernetes deployment: Closed
• Support user-specified annotations for the rest Service: Closed