tillrohrmann commented on a change in pull request #9470: [FLINK-13380][k8s]
Improve the usability of Flink session cluster on Kubernetes
URL: https://github.com/apache/flink/pull/9470#discussion_r315254620
##########
File path: docs/ops/deployment/kubernetes.md
##########
@@ -54,20 +54,31 @@ A basic Flink session cluster deployment in Kubernetes has
three components:
Using the resource definitions for a [session
cluster](#session-cluster-resource-definitions), launch the cluster with the
`kubectl` command:
+ kubectl create -f configmap.yaml
kubectl create -f jobmanager-service.yaml
kubectl create -f jobmanager-deployment.yaml
kubectl create -f taskmanager-deployment.yaml
+Note that you could define your own customized options of `flink-conf.yaml`
within `configmap.yaml`.
+
You can then access the Flink UI via `kubectl proxy`:
1. Run `kubectl proxy` in a terminal
2. Navigate to
[http://localhost:8001/api/v1/namespaces/default/services/flink-jobmanager:ui/proxy](http://localhost:8001/api/v1/namespaces/default/services/flink-jobmanager:ui/proxy)
in your browser
+Another way to view the Flink UI is via [service with
NodePort](https://kubernetes.io/docs/tasks/access-application-cluster/service-access-application-cluster/#creating-a-service-for-an-application-running-in-two-pods)
Review comment:
```suggestion
In order to view the Flink's web UI, it needs to be exposed via a Kubernetes
service which exposes the port on the node's public ip. The service
`flink-jobmanager-svc` achieves exactly this. Using this service, the web ui
can be accessed via `http://<public-node-ip>:<node-port>`.
```
----------------------------------------------------------------
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]
With regards,
Apache Git Services
