wangyang0918 commented on a change in pull request #14006:
URL: https://github.com/apache/flink/pull/14006#discussion_r521791380
##########
File path: docs/ops/jobmanager_high_availability.md
##########
@@ -215,6 +215,74 @@ Starting zookeeper daemon on host localhost.</pre>
<pre>
$ bin/yarn-session.sh -n 2</pre>
+## Kubernetes Cluster High Availability
+We are using a
[deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/)
for the JobManager when deploying Flink on Kubernetes cluster. The `replicas`
is configured to 1, which means that a new JobManager will be launched to take
over the leadership once the current one terminated exceptionally.
Review comment:
Hmm, I think "running Flink as a Kubernetes deployment" is not accurate.
Because we are running Flink JobManager as a Kubernetes deployment. Do you
think the following sentences make sense?
When running Flink JobManager as a Kubernetes
[deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/),
the `replica` count should be configured to 1 or greater.
* The value `1` means that a new JobManager will be launched to take over
leadership if the current one terminates exceptionally.
* The value `N`(greater than 1) means that multiple JobManagers will be
launched while one is active and others are standby. Starting more than one
JobManager will make the recovery faster.
----------------------------------------------------------------
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]
