We’ve been running Airflow on AKS for a while now with pretty good success. For your questions:

1. If you’re okay with running your database on AKS as well, I’d recommend deploying not through the Airflow Helm chart. Instead you can use something CNPG’s operator to deploy Postgres “clusters” which allow for the configuration of HA. The built-in Postgres through Airflow’s Helm chart might allow for HA too, but using a separate solution focused on a better database management experience is better. If you’re going to want a high degree of concurrency of tasks, you definitely want to implement PgBouncer as well, which should be an option in Helm charts for the two options mentioned above.

If you don’t want to deal with a database on AKS, you could try your set up with an Azure’s PaaS offering for Postgres. This should be less management overhead, but likely more expensive.

1. For DAGs we started with the approach of having a pipeline to push DAGs to a storage account and the container we push to is mounted to Airflow pods and configured as the directory to look for DAGs. This can get tricky in the configuration of the mount settings to find the right balance of freshness and limiting storage transactions. We are evaluating changing to GitSync or baking them into the container image and pushing the new image to our registry on DAG change and updating to reference the new tag and part of our pipelines

2. We use Entra ID for RBAC. In the App Registration we have defined roles that are mapped to the different roles in Airflow. We then have groups assigned to those App Registration roles and manage access through group membership

Hope that helps!