AIrflow 3 - API Server health check issue

[sargish-vertex]

Apache Airflow version

3.0.6

If "Other Airflow 2 version" selected, which one?

No response

What happened?

Airflow api-server still sending request to outdated api

│ INFO: 100.120.1.89:44816 - "GET /api/v1/version HTTP/1.1" 404 Not Found ││ INFO: 100.120.85.157:40790 - "GET /api/experimental/test HTTP/1.1" 404 Not Found ││ INFO: 10.10.134.231:59374 - "GET /api/v2/version HTTP/1.1" 200 OK ││ INFO: 10.10.134.231:59382 - "GET /api/v2/version HTTP/1.1" 200 OK ││ INFO: 100.120.1.89:46410 - "GET /api/v1/version HTTP/1.1" 404 Not Found ││ INFO: 100.120.85.157:59714 - "GET /api/experimental/test HTTP/1.1" 404 Not Found ││ INFO: 10.10.134.231:48560 - "GET /api/v2/version HTTP/1.1" 200 OK ││ INFO: 10.10.134.231:48570 - "GET /api/v2/version HTTP/1.1" 200 OK

What you think should happen instead?

No response

How to reproduce

airflow install with default settings

Operating System

linux, k8s

Versions of Apache Airflow Providers

No response

Deployment

Official Apache Airflow Helm Chart

Deployment details

No response

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[bot]]

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.

[potiuk]

You have not specified which version of chart you use - but I believe in latest version there are no /experimenta or /v1 calls - maybe you have old version or maybe you use different chart (not the one released by Airflow team) or maybe you have some custom health-checks configured.

Converting to a discussion until it is clarified.

[chandakanant]

I am also facing the same issue. I am using the 1.18.0 chart version.

• Logs
  api-server "GET /api/v2/version HTTP/1.1" 404 462 "-" "kube-probe/1.32+

[amoghrajesh]

Have you deployed it with a base_url or some custom setting?

[chandakanant]

Yes @amoghrajesh, I am passing it as extraEnv in my values.yaml

extraEnv: |

• name : AIRFLOW__WEBSERVER__BASE_URL
  value: 'https://airflow-test.com'

[aayostem]

The 404 errors you're seeing are caused by outdated health checks trying to access deprecated API endpoints (/api/v1/ and /api/experimental/) while Airflow 3 uses /api/v2/.
FYI /api/v1/version has been deprecated.

i'll advice you to update Kubernetes Health Checks

Update your Helm values.yaml to use the correct API endpoints:

# values.yaml
healthChecks:
  enabled: true
  apiServer:
    livenessProbe:
      httpGet:
        path: /api/v2/version
        port: http
    readinessProbe:
      httpGet:
        path: /api/v2/version
        port: http

# If you're using custom base_url, ensure it's properly configured
config:
  webserver:
    base_url: https://airflow-test.com

extraEnv:
  - name: AIRFLOW__WEBSERVER__BASE_URL
    value: 'https://airflow-test.com'