[bitnami/airflow] Unify and document production values

Signed-off-by: Carlos Rodriguez Hernandez <crhernandez@bitnami.com>
This commit is contained in:
Carlos Rodriguez Hernandez
2019-06-07 12:29:13 +00:00
parent f37e9a84d6
commit 27f9b732ff
3 changed files with 30 additions and 2 deletions

View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: airflow
version: 0.1.3
version: 0.1.4
appVersion: 1.10.3
description: Apache Airflow is a platform to programmatically author, schedule and monitor workflows.
keywords:

View File

@@ -165,6 +165,34 @@ $ helm install --name my-release -f values.yaml bitnami/airflow
> **Tip**: You can use the default [values.yaml](values.yaml)
### Production configuration
This chart includes a `values-production.yaml` file where you can find some parameters oriented to production configuration in comparison to the regular `values.yaml`:
- URL used to access to airflow web ui:
```diff
- # airflow.baseUrl:
+ airflow.baseUrl: http://airflow.local
```
- Number of Airflow Worker replicas:
```diff
- airflow.worker.replicas: 1
+ airflow.worker.replicas: 3
```
- Force users to specify a password:
```diff
- airflow.auth.forcePassword: false
+ airflow.auth.forcePassword: true
```
- Enable ingress controller resource:
```diff
- ingress.enabled: false
+ ingress.enabled: true
```
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.

View File

@@ -112,7 +112,7 @@ airflow:
# configurationConfigMap:
## Name of an existing config map containing all the DAGs files you want to load in Airflow.
##
# dagsConfigMap:
## dagsConfigMap:
## Airflow generic configuration
##
loadExamples: false