Yinan Li

Please update the chart version.

Looks like you need to bump the version again.

Sorry about it, but looks like another conflict in Chart.yaml needs to be resolved.

Can you elaborate more on this?

We support defining environment variables from secret data (https://kubernetes.io/docs/tasks/inject-data-application/distribute-credentials-secure/#define-container-environment-variables-using-secret-data). See https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/blob/master/docs/user-guide.md#using-secrets-as-environment-variables.

Thanks for bringing it up! This is a great topic to discuss. Option 2 definitely works by mounting a pre-created secret containing the keytab and principal into the operator pod,...

I think we can implement both options. For option 2, the secret storing the keytab and principal gets mounted into the operator pod. Additionally, we need a new optional field...

> 'm not sure if the spark.kubernetes.driver.secrets.[SecretName] are mounted before start-up we could potentially use those and check in the operator if one named keytab exist or some special keyword....

> Did you mean to say the driver pod? Otherwise I'm a bit confused how this case is handled for passing in the keytab during the spark-submit call. No, I...

Thanks for willing to take on this! I think we can use separate PRs for the two options. For option 1, i.e., mounting a secret storing the keytab into the...