ja-michel opened a new issue, #58625:
URL: https://github.com/apache/airflow/issues/58625
### Official Helm Chart version
1.18.0 (latest released)
### Apache Airflow version
3.1.3
### Kubernetes Version
v1.33.5-eks
### Helm Chart configuration
```
...
airflow:
digest:
sha256:1ba822595cc6d29a9afaf213e5015ee56c0d77c2795d8e095df65a33dee318cf
pullPolicy: IfNotPresent
repository: <account>.dkr.ecr.<region>.amazonaws.com/airflow
tag: latest
pod_template:
repository: ~
tag: ~
pullPolicy: Always
```
### Docker Image customizations
_No response_
### What happened
When updating the image and maintaining the same tag, for example `latest`,
the airflow containers will be updated correctly because the use the digest.
However the workers will be stuck using the stale version of `latest` that is
present in the node.
The pod template does not support using the image digest. See:
https://github.com/apache/airflow/blob/helm-chart/1.18.0/chart/templates/_helpers.yaml#L361
However the airflow images do, see:
https://github.com/apache/airflow/blob/helm-chart/1.18.0/chart/templates/_helpers.yaml#L350
### What you think should happen instead
The definition of `pod_template_image` should support the digest. With this
we can ensure the workers will use the correct image.
### How to reproduce
Create an image and tag with `latest`
Use the latest tag for all airflow images `images.airflow.tag` and leave the
`images.pod_template.*` values unset.
Run a task
Create a new image and tag it with `latest`
Update the `images.airflow.digest` to the digest of the new image. Airflow
images run with the correct image - digest takes precedence over tag.
Run a task again.
The worker is created with the stale image with tag `latest` the digest in
the airflow values section is ignored.
### Anything else
_No response_
### Are you willing to submit PR?
- [x] 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]
