I would like to introduce and propose a feature I have personally implemented in the SparkSubmitHook for managing Spark connections.
This feature focuses on managing the Kerberos-related principal and keytab within the connection settings.
The basic idea is to store the keytab as a base64 encoded credential. When submitting a Spark job, the credential is decoded and saved as a file, and its path is specified during the submission.
Use case/motivation
Setting up the keytab for each worker can be challenging, and managing the keytab each time it changes can be cumbersome. By storing this information within the connection, we can reduce the need to deploy the keytab every time.
I would appreciate your consideration of this proposal.
Description
Hello,
I would like to introduce and propose a feature I have personally implemented in the SparkSubmitHook for managing Spark connections.
This feature focuses on managing the Kerberos-related principal and keytab within the connection settings.
The basic idea is to store the keytab as a base64 encoded credential. When submitting a Spark job, the credential is decoded and saved as a file, and its path is specified during the submission.
Use case/motivation
Setting up the keytab for each worker can be challenging, and managing the keytab each time it changes can be cumbersome. By storing this information within the connection, we can reduce the need to deploy the keytab every time.
I would appreciate your consideration of this proposal.
Thank you.
Related issues
No response
Are you willing to submit a PR?
Code of Conduct