A values.yaml file parameterizes a Helm chart deployment by overriding selected defaults. Helm applies it during installation or upgrade, letting an Airflow deployment adopt project-specific users, images, databases, secrets, DAG sources, and executors. section 17.2.4 section 17.4
Typical overrides include:
- Select a custom Docker image by setting images.airflow.repository and images.airflow.tag, then deploy it with helm upgrade. section 17.2.7
- Choose DAG delivery through a persistent volume or Git synchronization, using dags.persistence or dags.gitSync settings. section 17.2.7
- Configure multiple executors and task images, including CeleryExecutor and KubernetesExecutor combinations. section 17.2.9
Apply an Airflow override file
Store deployment choices in /etc/helm/values/01-user-values.yaml, then apply them with: helm upgrade --install airflow apache-airflow/airflow --namespace airflow --set apiServer.service.type=LoadBalancer -f /etc/helm/values/01-user-values.yaml. Upgrading changes the configuration without necessarily removing existing resources; an old user can therefore remain after a new initial-user setting is applied. section 17.2.4


