jay-olulana commented on issue #21943:
URL: https://github.com/apache/airflow/issues/21943#issuecomment-1471890234
Hi @potiuk, Sorry that the reply is late. But I did apply your fix after
upgrading to `Helm 1.8.0`, but the error persists. Although I think this is a
`false positive`.
Below are the steps I took;
- As you know, I have airflow deployed via `helm` using terraform to an EKS
Cluster.
- EKS Cluster has k8s `1.23`
- Helm Chart Version for Airflow is `1.8.0`
- I added the following to my `overrides.yaml`
```yaml
createUserJob:
useHelmHooks: false
applyCustomEnv: false
migrateDatabaseJob:
useHelmHooks: false
applyCustomEnv: false
ttlSecondsAfterFinished: 300
```
- Then I nuked the chart (destroyed the entire `airflow` namespace on EKS)
- Recreated airflow with an image tag. Say, `v1.1.0`
- Updated the image tag with a new version, `v1.1.1`
- Run `terraform apply` and this error pops up again;
**Good News** is that my airflow pods are recreated in EKS with the new tags
and are healthy.
But terraform fails the apply.
Hope this provides some insights.
--
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]
