1e651dc3c3
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 each Job template 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: Ib5a7eb494fb776d74e1edc767b9522b02453b19d |
||
|---|---|---|
| .. | ||
| bin | ||
| certificates.yaml | ||
| configmap-bin.yaml | ||
| configmap-etc.yaml | ||
| deployment.yaml | ||
| ingress.yaml | ||
| job-db-drop.yaml | ||
| job-db-init.yaml | ||
| job-db-migrate.yaml | ||
| job-db-sync.yaml | ||
| job-image-repo-sync.yaml | ||
| job-ks-endpoints.yaml | ||
| job-ks-service.yaml | ||
| job-ks-user.yaml | ||
| network_policy.yaml | ||
| pdb.yaml | ||
| secret-db.yaml | ||
| secret-ingress-tls.yaml | ||
| secret-keystone.yaml | ||
| service-ingress.yaml | ||
| service.yaml | ||