[D] API Server Issue [airflow]

["chandakanant (via GitHub)" <gi...@apache.org>]

GitHub user chandakanant created a discussion: API Server Issue

I have installed Airflow Helm version 1.18.0 on the EKS cluster (1.32). I am facing multiple issues, like -
1.  ```airflow command error: argument GROUP_OR_COMMAND: invalid choice: 'api-server' (choose from 'celery', 'cheat-sheet', 'config', 'connections', 'dag-processor', 'dags', 'db', 'info', 'jobs', 'kerberos', 'kubernetes', 'plugins', 'pools', 'providers', 'roles', 'rotate-fernet-key', 'scheduler', 'standalone', 'sync-perm', 'tasks', 'triggerer', 'users', 'variables', 'version', 'webserver'), see help above.```

Original value in values.yaml - ```args: ["bash", "-c", "exec airflow api-server"]```
Updated - ```args: ["bash", "-c", "exec airflow webserver"]```

**Question:** Is this expected in Airflow 3.x / Helm 1.18.0, given that api-server is not a valid Airflow command anymore?

2. Getting ```api-server 10.44.39.225 - - "GET /api/v2/version HTTP/1.1" 404 462 "-" "kube-probe/1.32+"``` 
- cannot change the probe paths in the Helm chart (not exposed in values.yaml).
- api/v2/version returns 404 because the endpoint doesn’t exist in my Airflow version.

Question: What is the recommended way to handle probes in this scenario when using Helm 1.18.0? Should we patch them post-install, or is there an official fix in the chart?

GitHub link: https://github.com/apache/airflow/discussions/56283

----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org