7803000a54
If labels are not specified on a Job, kubernetes defaults them to include the labels of their underlying Pod template. Helm 3 injects metadata into all resources [0] including a `app.kubernetes.io/managed-by: Helm` label. Thus when kubernetes sees a Job's labels they are no longer empty and thus do not get defaulted to the underlying Pod template's labels. This is a problem since Job labels are depended on by - Armada pre-upgrade delete hooks - Armada wait logic configurations - kubernetes-entrypoint dependencies Thus, for Job templates previously missed, this adds labels matching the underlying Pod template to retain the same labels that were present with Helm 2. [0]: https://github.com/helm/helm/pull/7649 Change-Id: Ie438b449a3d9853d786215d40a39c32d164e9950 |
||
---|---|---|
.. | ||
templates | ||
values_overrides | ||
.helmignore | ||
Chart.yaml | ||
requirements.yaml | ||
values.yaml |