Airflow Latest Helm chart is not compatible with 3.0.0 version

[vibhorbansal98]

Official Helm Chart version

1.16.0 (latest released)

Apache Airflow version

3.0.0

Kubernetes Version

1.26.4

Helm Chart configuration

I am managing my airflow deployment using argocd and using airflow helm chart 1.16.0.

  repoURL: https://airflow.apache.org/
  targetRevision: 1.16.0
  chart: airflow

Docker Image customizations

No modifications in the docker Image, i am pulling the official airflow 3.0.0 image.
FROM docker.repo1.uhc.com/apache/airflow:3.0.0

Requirements.txt -
#Vulnerabilites Fixes and Custom Airflow Providers
apache-airflow-providers-airbyte
apache-airflow-providers-postgres
authlib==1.3.1
cryptography==44.0.1
mysql-connector-python==9.1.0
dbt-core
dbt-snowflake==1.8.4
airflow-provider-great-expectations
snowflake-connector-python
great_expectations
apache-airflow-providers-snowflake
tornado==6.4.2
croniter
jinja2==3.1.6
openpyxl
apache-airflow-providers-microsoft-azure
apache-airflow-providers-mongo
werkzeug==3.0.6
apache-airflow-providers-common-sql
h11==0.16.0

What happened

I migrated from 2.10.5 version to 3.0.0, airflow-api-server pod is running but i am getting 404 error in ui.
After investigating i have found out that ingress file is not getting created in my namesapce.

On further checking i found out that 1.16.0 helm chart does not contain ingress file in the api-server -

But the ingress file is present in the airflow repo under chart -

As part of our company policy if we are using outside organisation helm chart we need to refer it directlty from the official docker hub and we can not store in our repo.

What you think should happen instead

Ingress file fix should be added in the official helm chart as well, as this is a breaking issue if we are using 3.0.0 version and 1.16.0 helm chart.

How to reproduce

Deploy using argocd
Helm chart - 1.16.0 and Airflow Version - 3.0.0
Ingress fill will not create in api-server app

Anything else

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

[gschuurman]

@vibhorbansal98 That's unfortunatly correct, the ingress has been added to main branch already. https://github.com/apache/airflow/blob/main/chart/templates/api-server/api-server-ingress.yaml
You could add this manually, I did the same for my deployment.

@jedcunningham perhaps a release of the helm chart can be done to fix this issue?

[vibhorbansal98]

@gschuurman thanks for the comment, as per our organization policy we can't store the helm chart in the repo. We need to directly refer it from official helm chart released by apache.

@jedcunningham it will be helpful if we get any update on the new helm chart version release date which fix the ingress issue.

[jedcunningham]

I don't have a hard release date, but I'm actually starting to work on it today.

[albundy83]

Hello,
if this PR and this one are merged, it will be a nice step for 3.0.0 support :)