Let’s say we have some DAGs in a Github repo with CI/CD that runs something like
astro deploy after tests pass. This should trigger a new deployment of Airflow, i.e. the image tag for that deployment will be updated. New webserver and scheduler Pods get initialized. This results in the Airflow UI being unavailable until the new deployments comes up.
First question: Am I understanding things correctly so far?
How would one go about creating / updating / deleting DAGs without having to redeploy a new webserver and scheduler, so users don’t experience UI downtime?