Warn about Kerberos init container removal in Chart 1.2x - #73390
Open
aaron-y-chen wants to merge 2 commits into
Open
aaron-y-chen wants to merge 2 commits into
aaron-y-chen wants to merge 2 commits into
Conversation
aaron-y-chen
marked this pull request as ready for review
September 19, 2026 23:42
aaron-y-chen
requested review from
Miretpl,
bugraoz93,
hussein-awala,
jedcunningham and
jscheffl
as code owners
September 19, 2026 23:42
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
related: #72555
Add deprecation warnings to the Chart 1.2x line for
kerberosInitContainersettings that will be removed in Chart 2.0.The warnings direct users to migrate legacy, Celery, Kubernetes, and Celery Worker Set configurations to the corresponding
kerberosSidecarsettings withstartupProbeenabled.Was generative AI tooling used to co-author this PR?
Generated-by: [Codex] following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.