johnstonmatt opened a new issue, #43247: URL: https://github.com/apache/airflow/issues/43247
### Official Helm Chart version 1.15.0 (latest released) ### Apache Airflow version chart default ### Kubernetes Version 1.28 ### Helm Chart configuration ```yaml targetRevision: 1.15.0 destinationNamespace: airflow repoURL: 'https://airflow.apache.org' chart: airflow values: executor: LocalKubernetesExecutor data: metadataSecretName: postgresql-connection-string-secret postgresql: enabled: false dags: gitSync: enabled: true repo: 'https://github.com/johnstonmatt/demo-dag-bag' credentialsSecret: airflow-git-credentials branch: main wait: 40 subPath: dags ``` ```yaml apiVersion: v1 kind: Secret metadata: name: airflow-git-credentials namespace: airflow stringData: GIT_SYNC_USERNAME: 'foousername' GIT_SYNC_PASSWORD: 'barpassword' # newly required by airflow-triggerer, in addition to the pre-existing keys above GITSYNC_USERNAME: 'foousername' GITSYNC_PASSWORD: 'barpassword' ``` ### Docker Image customizations _No response_ ### What happened `airflow-triggerer` needs the gitsync credentials to be formatted as `GITSYNC_USERNAME` and `GITSYNC_PASSWORD`, while the rest of the chart seems to require `GIT_SYNC_USERNAME` and `GIT_SYNC_PASSWORD` ### What you think should happen instead the airflow helm chart should adhere to only one format rather than requiring both ### How to reproduce If you need to reproduce: 1. Use [cndi](https://cndi.run/gh?utm_id=5111) to install `airflow` via ArgoCD: `cndi create ghusername/my-repo -t airflow` 2. after cluster is deployed and working, update from `targetRevision: '1.11.0'` to `targetRevision: '1.15.0'` ### Anything else _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
