fix: mount kerberos.keytab to worker when enable

[npsables]

I believe kerberos.keytab and others should be mounted to worker container when enabling kerberos. We may want to reuse these files, for example, to spark-submit jobs. Maybe #24369 is a good reference for this pr.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[potiuk]

Can you please add tests covering that one @npsables ? I think if you add tests, it will be immediately visible what effect it will have.

[npsables]

Hi sorry for late reply. I observed that my keytab cannot be found (in worker pods) when enabling Kerberos in helm, it doesn't make sense at all. People may want to use it for other services.

If you still think this is a good idea, I can create a testcase (check if kerberos.keytab exists after render) for this PR.

[potiuk]

If you still think this is a good idea, I can create a testcase (check if kerberos.keytab exists after render) for this PR.

Yes. Adding tests is useful to show that. We generally expect all the changes to be covered by tests. So showing tests especially ones that have assertions showing the behaviour you observed (and failing because of that if your change is not implemented) is exactly that is needed.

[npsables]

Hi, I added a testcase. Also I notice this function name is misspelled (keberos). Do you want me to change it too?

airflow/tests/charts/test_kerberos.py

Line 94 in 5ad2ed1

def test_keberos_sidecar_resources_are_not_added_by_default(self):

[potiuk]

Static checks need fixing.

[npsables]

All good now

[boring-cyborg]

Awesome work, congrats on your first merged pull request!

[potiuk]

Indeed.

[npsables]

This is actually the first time I have contributed to any opensource. It's meaningful to me. Thanks a lot!

[potiuk]

Cool. Maybe you would like to take part in this campaign? https://news.apache.org/foundation/entry/the-asf-launches-firstasfcontribution-campaign - fill-in a short form and the ASF marketing team will contact you if they would like to get more insight :)