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

Fuyao Li commented on FLINK-22264:
----------------------------------

Thanks. Please refer to the PR I submitted for details. 
https://github.com/apache/flink/pull/15602

> Fix misleading statement about per-job mode support for Kubernetes in 
> Concept/Flink Architecture page
> -----------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-22264
>                 URL: https://issues.apache.org/jira/browse/FLINK-22264
>             Project: Flink
>          Issue Type: Task
>          Components: Documentation
>    Affects Versions: 1.12.2
>            Reporter: Fuyao Li
>            Assignee: Fuyao Li
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.13.0
>
>
> I noticed a conflict in the document for per-job mode support for Kubernetes.
> In the doc here [1], it mentions
> in a Flink Job Cluster, the available cluster manager (like YARN or 
> Kubernetes) is used to spin up a cluster for each submitted job and this 
> cluster is available to that job only.
> It implies per job mode is supported in Kubernetes.
>  
> However, in the docs [2] and [3], it clearly points out per-job mode is not 
> supported in Kubernetes.
>  
> To avoid the misunderstanding, I think we should fix the statement in the 
> concept page. I had a discussion with Yang Wang on flink user mailing list 
> earlier. (link still not available in the archive for now.)
>  
> [1] 
> [https://ci.apache.org/projects/flink/flink-docs-master/docs/concepts/flink-architecture/#flink-job-cluster]
> [2] 
> [https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#per-job-cluster-mode]
> [3] 
> [https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/resource-providers/standalone/kubernetes/]



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

Reply via email to