Vedrillan commented on issue #32482:
URL: https://github.com/apache/airflow/issues/32482#issuecomment-1630246032
@rzjfr sure here are all the info
I am using helm v3.12.0.
The main Chart.yml looks something like this:
```
apiVersion: v2
name: infra-helm
description: infrastructure bundle for install and maintaining kubernetes
clusters
type: application
version: "1.0.0"
appVersion: "2023-04-06"
dependencies:
- condition: airflow.enabled
name: airflow
repository: https://airflow.apache.org
version: 1.10.0
```
Ofc it has more dependencies but I do not think it make much difference to
have them or not.
The values are spread across 3 files, 1 global, 1 for env and 1 for
sensitive data, but once "merged" it should be like this:
```
airflow:
enabled: true
ingress:
web:
enabled: true
hosts:
- name: "airflow.example.com"
tls:
enabled: true
secretName: "airflow-web-tls"
annotations:
nginx.ingress.kubernetes.io/whitelist-source-range: 0.0.0.0/0
nginx.ingress.kubernetes.io/service-upstream: "true"
kubernetes.io/tls-acme: "true"
webserver:
defaultUser:
role: Admin
username: admin
email: [email protected]
firstName: John
lastName: Doe
password: "xXx"
executor: "KubernetesExecutor"
logs:
persistence:
enabled: true
redis:
enabled: false
```
Then I run the upgrade with helm `helm upgrade -n clusterwide infra-helm .
-f values.d/staging.yaml -f values.d/staging.secret.yaml --reset-values
--atomic --debug --install --create-namespace` and finally get the error
previously mentioned.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]