Hello
I am working on the kubernetes helm chart for airflow, based on this container.
I wonder it it would make sense to split the wait for the databases + initdb out of the web instance?
When we create 2 instances of the web container, they both have to wait for the postgres and the redis server, then they both perform the initdb operation. Can't this be done on the scheduler instance which for the moment needs to be unique?
Proposal: move these lines:
wait_for_port "Postgres" "$POSTGRES_HOST" "$POSTGRES_PORT"
wait_for_redis
airflow initdb
in the scheduler section.
Another option would be to move initdb into a separate section in entrypoint.sh. This would allow the use of an init container in Kubernetes.
@puckel what do you think about it?
Most helpful comment
Another option would be to move initdb into a separate section in entrypoint.sh. This would allow the use of an init container in Kubernetes.