Yang Wang created FLINK-16760:
---------------------------------
Summary: Support the yaml file submission for native Kubernetes
integration
Key: FLINK-16760
URL: https://issues.apache.org/jira/browse/FLINK-16760
Project: Flink
Issue Type: New Feature
Components: Deployment / Kubernetes, Deployment / Scripts
Reporter: Yang Wang
Currently, the native K8s integration is friendly and convenient to the Flink
users, especially they have some experience of YARN deployment. The submission
command and process are very similar and could be integrated into their
existing deployer(i.e. job lifecycle management system).
However, if you are a K8s user and prefer the K8s way to start the Flink
cluster(regarding it as a application). Then yaml way is more appropriate.
What's the difference between standalone on K8s[1] and this ticket?
# Dynamic resource allocation
# Do not need to create taskmanager deployment yaml. Since the taskmanagers
will be allocated by Flink ResourceManager dynamically on demand.
# Service account needs to be prepared beforehand[2].
# Some scripts(flink-console.sh, jobmanager.sh, etc.) needs to be updated to
use native K8s entrypoint
{{org.apache.flink.kubernetes.entrypoint.KubernetesSessionClusterEntrypoint}}
[1].
[https://ci.apache.org/projects/flink/flink-docs-master/ops/deployment/kubernetes.html]
[2].
[https://ci.apache.org/projects/flink/flink-docs-master/ops/deployment/native_kubernetes.html#rbac]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
