FuyaoLi2017 opened a new pull request #15602:
URL: https://github.com/apache/flink/pull/15602


   
   ## What is the purpose of the change
   I noticed a conflict in the document statement 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 
Flink Architecture page and add an extra hint note here. I had a discussion 
with @wangyang0918  on flink user mailing list earlier on this issue and he 
agrees to patch such a change.
   
    
   [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/
   
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (no)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (no)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (no)
     - If yes, how is the feature documented? (docs)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to