huynhsontung opened a new pull request, #66616:
URL: https://github.com/apache/airflow/pull/66616

   Agent-Logs-Url: 
https://github.com/huynhsontung/airflow/sessions/be394b63-9852-4a0f-a4b9-6d9e14c14f29
   
    <!-- SPDX-License-Identifier: Apache-2.0
         https://www.apache.org/licenses/LICENSE-2.0 -->
   
   <!--
   Thank you for contributing!
   
   Please provide above a brief description of the changes made in this pull 
request.
   Write a good git commit message following this guide: 
http://chris.beams.io/posts/git-commit/
   
   Please make sure that your code changes are covered with tests.
   And in case of new features or big changes remember to adjust the 
documentation.
   
   Feel free to ping (in general) for the review if you do not see reaction for 
a few days
   (72 Hours is the minimum reaction time you can expect from volunteers) - we 
sometimes miss notifications.
   
   In case of an existing issue, reference it using one of the following:
   
   * closes: #ISSUE
   * related: #ISSUE
   -->
   
   ## Summary
   
   Adds `ipFamilyPolicy` and `ipFamilies` fields to all Airflow Helm chart 
service templates to support IPv6 and dual-stack networking configurations.
   
   ## Changes
   
   ### Service Templates Updated
   All 9 service templates now conditionally include `ipFamilyPolicy` and 
`ipFamilies` when set:
   - `api-server-service.yaml`
   - `flower-service.yaml`
   - `redis-service.yaml`
   - `pgbouncer-service.yaml`
   - `statsd-service.yaml`
   - `otel-collector-service.yaml`
   - `worker-service.yaml` (headless)
   - `triggerer-service.yaml` (headless)
   - `scheduler-service.yaml` (headless)
   
   ### `values.yaml`
   - Added `ipFamilyPolicy: ~` and `ipFamilies: []` defaults to all service 
sections
   - Added new `service:` sections to `workers`, `scheduler`, and `triggerer` 
(previously had no configurable service options)
   - Defaults are `null`/empty, preserving existing behavior unless explicitly 
set
   
   ### `values.schema.json`
   - Added `ipFamilyPolicy` with enum validation (`SingleStack`, 
`PreferDualStack`, `RequireDualStack`, or `null`)
   - Added `ipFamilies` with item enum validation (`IPv4`, `IPv6`)
   - Added `service` property definitions for `workers`, `scheduler`, and 
`triggerer`
   
   ### Tests
   Added tests to all relevant test files verifying:
   - `ipFamilyPolicy` and `ipFamilies` are rendered when configured
   - Neither field is present by default (no breaking change)
   
   ## Usage Example
   
   ```yaml
   # Enable dual-stack on the API server
   apiServer:
     service:
       ipFamilyPolicy: PreferDualStack
       ipFamilies:
         - IPv4
         - IPv6
   
   # Force IPv6-only on redis
   redis:
     service:
       ipFamilyPolicy: SingleStack
       ipFamilies:
         - IPv6
   ```
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   <!--
   If generative AI tooling has been used in the process of authoring this PR, 
please
   change below checkbox to `[X]` followed by the name of the tool, uncomment 
the "Generated-by".
   -->
   
   - [x] Yes (please specify the tool below)
   GitHub Copilot (Claude Sonnet 4.6)
   
   <!--
   Generated-by: [Tool Name] following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   -->
   
   ---
   
   * Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information. Note: commit author/co-author name and email in commits 
become permanently public when merged.
   * For fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   * When adding dependency, check compliance with the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: 
`{pr_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
 You can add this file in a follow-up commit after the PR is created so you 
know the PR number.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to