Skip to content

Add support for Kubernetes Gateway API (HTTPRoute) in Helm Chart #61452

Closed

Description

@prakharcode

Description

Currently, the official Apache Airflow Helm chart only supports the standard Kubernetes Ingress API. Many modern Kubernetes environments are migrating to the Kubernetes Gateway API.

I would like the Helm chart to include optional templates for Gateway API resources, specifically:

HTTPRoute: Support for routing traffic to the Webserver, Flower, and API Server.

Configuration Values: New sections in values.yaml (e.g., gateway.enabled, gateway.web.hostnames, gateway.web.parentRefs) similar to the existing ingress configuration.

The Gateway API is now GA and is becoming the standard for networking in Kubernetes 1.24+.

Use case/motivation

No response

Related issues

The only related discussion I have found: #51967

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Activity

  1. abhijeets25012-tech commented on Feb 5, 2026

    @abhijeets25012-tech
    Contributor

    I would like to contribute

  2. prakharcode commented on Feb 5, 2026

    @prakharcode
    ContributorAuthor

    Hi @abhijeets25012-tech, I would like to take it up already, will start working on a PR soon, you're welcome to help with reviews and testing!

  3. WhiteDiamondz commented on Apr 16, 2026

    @WhiteDiamondz

    Hey @prakharcode !

    Have you had any chance to work on this ? I recently encountered the need for HTTPRoute support and could work on a merge request if necessary.

    Thanks !

  4. Miretpl commented on Apr 16, 2026

    @Miretpl
    Contributor

    In general, anyone can work on this issue, and if at the same time, we have more than one PR, we will choose the best one, so I encourage anyone to work on this. For more details, you can also check the https://github.com/apache/airflow/blob/main/contributing-docs/04_how_to_contribute.rst#contribute-code-changes doc, as the handling of the issues was changed not so long ago.

    Just a slight note too - the Helm Chart itself is during the refurbish discussion, so there is a chance that this feature will be delayed until e.g. Helm Chart 2.0, which currently does not have a release date.

  5. somaz94 commented on May 29, 2026

    @somaz94
    Contributor

    Working on this — draft PR opened: #67675

  6. removed
    needs-triagelabel for new issues that we didn't triage yet
    on Jul 16, 2026
  7. Miretpl commented on Jul 22, 2026

    @Miretpl
    Contributor

    Looking at the current state, we are missing the HTTPRoute for the Webserver component for the 1.2x chart line (chart/v1-2x-test) branch (Airflow 2.11 is supported in the 1.2x line), so if anyone would like to implement it, that would be great!

  8. aaron-y-chen commented on Jul 24, 2026

    @aaron-y-chen
    Contributor

    Oh my bad, I thought the Flower HTTPRoute was the last part. Let me handle Webserver component for the 1.2x chart as well.

  9. Miretpl commented on Aug 1, 2026

    @Miretpl
    Contributor

    All finished so closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions