Establishing init container + sidecar model for airflow kerberos #35548
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per the discussion here: #35146 (comment)
We have backend support for running airflow in a init container model as well as a sidecar model while running airflow with kubernetes. It only makes sense to naturally have the ability to enable the airflow kerberos init container in our helm charts while running the airflow worker with kerberos (the token would be refreshed when airflow starts).
This will also serve as an example to someone wanting to use airflow kerberos in this fashion.
However, since this is a new feature, we need to add it only in 2.8.0 and up, hence the semver.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.