[GitHub] alpinegizmo commented on a change in pull request #6561: [FLINK-10001][docs] Update Docker and Kubernetes documentation

[GitBox <gi...@apache.org>]

alpinegizmo commented on a change in pull request #6561: [FLINK-10001][docs] Update Docker and Kubernetes documentation
URL: https://github.com/apache/flink/pull/6561#discussion_r210522820
 
 

 ##########
 File path: docs/ops/deployment/kubernetes.md
 ##########
 @@ -23,51 +23,78 @@ specific language governing permissions and limitations
 under the License.
 -->
 
-[Kubernetes](https://kubernetes.io) is a container orchestration system.
+This page describes how to deploy a Flink job and session cluster on [Kubernetes](https://kubernetes.io).
 
 * This will be replaced by the TOC
 {:toc}
 
-## Simple Kubernetes Flink Cluster
+## Setup Kubernetes
 
-A basic Flink cluster deployment in Kubernetes has three components:
+Please follow [Kubernetes' setup guide](https://kubernetes.io/docs/setup/) in order to deploy a Kubernetes cluster.
+If you want to run Kubernetes locally, we recommend using [MiniKube](https://kubernetes.io/docs/setup/minikube/).
 
-* a Deployment for a single Jobmanager
-* a Deployment for a pool of Taskmanagers
-* a Service exposing the Jobmanager's RPC and UI ports
+<div class="alert alert-info">
+  <strong>Note:</strong> If using MiniKube please make sure to execute <code>minikube ssh 'sudo ip link set docker0 
+  promisc on'</code> before deploying a Flink cluster. Otherwise Flink components are not able to self reference 
+  themselves through a Kubernetes service. 
+</div>
 
-### Launching the cluster
+## Flink session cluster on Kubernetes
 
-Using the [resource definitions found below](#simple-kubernetes-flink-cluster-
-resources), launch the cluster with the `kubectl` command:
+A Flink session cluster is executed as a long running Kubernetes Deployment. 
+Note that you can run multiple Flink jobs on a session cluster.
+Each job needs to be submitted to the cluster after it has been deployed.
 
 Review comment:
   "it" feels a bit ambiguous here. How about
   
   Each job needs to be submitted to the cluster after the cluster has been deployed.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services