[chart/v1-2x-test] Chart: Fix Airflow 3 task log access with NetworkPolicies (#65754)#67805
Merged
potiuk merged 1 commit intoMay 31, 2026
Conversation
(cherry picked from commit 8b2ce00)
jscheffl
approved these changes
May 31, 2026
1 task
This was referenced May 31, 2026
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
3 participants
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.
Backport of #65754 to the 1.x Helm chart line (chart/v1-2x-test).
On Airflow 3, task logs are served by the
api-servercomponent, but the1.x chart's NetworkPolicy ingress rules for the scheduler, triggerer, and
worker still allow log traffic only from the legacy
webservercomponent.With
networkPolicies.enabled=true, this blocks the API server fromreading task logs. This retargets the three log-ingress selectors to
component: api-serverand adds rendering tests for each.Cherry-picked from 8b2ce00 (the two scheduler/triggerer template hunks
were adapted by hand: the 1.x base used
component: webserverwhere mainused
scheduler/triggerer, all corrected toapi-server).Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines