From 82275ae5684f650e273c27fbda65ed87893ebd6b Mon Sep 17 00:00:00 2001
From: Andrew Ash <andrew@andrewash.com>
Date: Fri, 24 Feb 2017 16:29:05 -0800
Subject: [PATCH] Document blocking submit calls (#152)

* Document blocking submit calls

https://github.com/apache-spark-on-k8s/spark/pull/53 added these config but didn't document them

* Update running-on-kubernetes.md
---
 docs/running-on-kubernetes.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/docs/running-on-kubernetes.md b/docs/running-on-kubernetes.md
index cddc7259e6ac3..9d49ac6829723 100644
--- a/docs/running-on-kubernetes.md
+++ b/docs/running-on-kubernetes.md
@@ -202,6 +202,21 @@ from the other deployment modes. See the [configuration page](configuration.html
     resource. Use alternatives such as Ingress if possible.
   </td>
 </tr>
+<tr>
+  <td><code>spark.kubernetes.submit.waitAppCompletion</code></td>
+  <td><code>true</code></td>
+  <td>
+    In cluster mode, whether to wait for the application to finish before exiting the launcher process.  When changed to
+    false, the launcher has a "fire-and-forget" behavior when launching the Spark job.
+  </td>
+</tr>
+<tr>
+  <td><code>spark.kubernetes.report.interval</code></td>
+  <td><code>1s</code></td>
+  <td>
+    Interval between reports of the current Spark job status in cluster mode.
+  </td>
+</tr>
 </table>
 
 ## Current Limitations