Getting Airflow 404 = Lots of circles Error

[Kapildev2018]

Hi Astronomer Team,

We are deploying this chart in our K8 cluster to run airflow. We are using nginx proxy to route to airflow. All pods & services are running. But while accessing the airflow URL we are getting Airflow 404 = Lots of circles Error. Is this because we have not set ingress.baseDomain while installing chart?

Please help.
Thanks,
Kapil.

[jedcunningham]

Hi Kapil,

You didn't mention what version of the chart you are on so I'll assume you are relatively up to date.

You'll sometimes see that if you haven't set the correct base_url (one way is via airflow.config.webserver.base_url). That would be what I would try first.

This chart now uses the official OSS chart as a subchart for the bulk of the heavy lifting, so you can always tap those community resources as well.

[Kapildev2018]

H

Hi Kapil,

You didn't mention what version of the chart you are on so I'll assume you are relatively up to date.

You'll sometimes see that if you haven't set the correct base_url (one way is via airflow.config.webserver.base_url). That would be what I would try first.

This chart now uses the official OSS chart as a subchart for the bulk of the heavy lifting, so you can always tap those community resources as well.

Hi Jed,

We are using airflow-1.7.6 chart

NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
airflow airflow 1 2023-02-08 07:25:28.732235529 +0000 UTC deployed airflow-1.7.6 2.0.0

We have to set it while installing as below or some other way?

helm install airflow --namespace airflow astronomer/airflow --set ingress.baseDomain=domain.com/airflow

I tried above still same error is coming..

All the pods & services are up.

NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
airflow airflow 1 2023-02-09 09:54:58.76522498 +0000 UTC deployed airflow-1.7.6 2.0.0
ubuntu@Bastion:~$ kubectl get all -n airflow
NAME READY STATUS RESTARTS AGE
pod/airflow-postgresql-0 1/1 Running 0 110s
pod/airflow-scheduler-548974997-d99tx 2/2 Running 0 110s
pod/airflow-statsd-644b8d9648-d72mf 1/1 Running 0 110s
pod/airflow-webserver-6f9d66c784-mq9p4 1/1 Running 0 110s

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/airflow-postgresql ClusterIP 10.0.230.178 5432/TCP 110s
service/airflow-postgresql-headless ClusterIP None 5432/TCP 110s
service/airflow-statsd ClusterIP 10.0.223.214 9125/UDP,9102/TCP 110s
service/airflow-webserver ClusterIP 10.0.140.16 8080/TCP 110s

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/airflow-scheduler 1/1 1 1 110s
deployment.apps/airflow-statsd 1/1 1 1 110s
deployment.apps/airflow-webserver 1/1 1 1 110s

NAME DESIRED CURRENT READY AGE
replicaset.apps/airflow-scheduler-548974997 1 1 1 110s
replicaset.apps/airflow-statsd-644b8d9648 1 1 1 110s
replicaset.apps/airflow-webserver-6f9d66c784 1 1 1 110s

NAME READY AGE
statefulset.apps/airflow-postgresql 1/1 110s

Thanks,
Kapil.

[jedcunningham]

Try with a --set airflow.config.webserver.base_url=http://domain.com/airflow as well.

If you are just starting down your Airflow on k8s journey, you'd be better off using the Apache Airflow chart instead of ours.