Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/21669#discussion_r223512267
--- Diff: docs/running-on-kubernetes.md ---
@@ -820,4 +820,37 @@ specific to Spark on Kubernetes.
This sets the major Python version of the docker image used to run the
driver and executor containers. Can either be 2 or 3.
</td>
</tr>
+<tr>
+ <td><code>spark.kubernetes.kerberos.krb5.location</code></td>
+ <td><code>(none)</code></td>
+ <td>
+ Specify the local location of the krb5 file to be mounted on the driver
and executors for Kerberos interaction.
+ It is important to note that for local files, the KDC defined needs to
be visible from inside the containers.
+ </td>
+</tr>
+<tr>
+ <td><code>spark.kubernetes.kerberos.krb5.configMapName</code></td>
+ <td><code>(none)</code></td>
+ <td>
+ Specify the name of the ConfigMap, containing the krb5 file, to be
mounted on the driver and executors
+ for Kerberos interaction. The KDC defined needs to be visible from
inside the containers. The ConfigMap must also
+ be in the same namespace of the driver and executor pods.
+ </td>
+</tr>
+<tr>
+ <td><code>spark.kubernetes.kerberos.tokenSecret.name</code></td>
+ <td><code>(none)</code></td>
+ <td>
+ Specify the name of the secret where your existing delegation token is
stored. This removes the need for the job user
+ to provide any keytab for launching a job.
+ </td>
+</tr>
+<tr>
+ <td><code>spark.kubernetes.kerberos.tokenSecret.itemKey</code></td>
+ <td><code>(none)</code></td>
+ <td>
+ Specify the item key of the data where your existing delegation token
is stored. This removes the need for the job user
+ to provide any keytab for launching a job.
--- End diff --
Same question as above.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
