Closed seh closed 5 months ago
It also shows this way:
$ kustomize version
unknown
/triage accepted /kind bug
The kustomize version
issue was resolved today with the release of Kustomize 5.4.1: https://github.com/kubernetes-sigs/kustomize/releases/tag/kustomize%2Fv5.4.1
Could you please confirm whether the issue still happens with the YAML rendering?
Could you please confirm whether the issue still happens with the YAML rendering?
Yes, that fixed the problem. The field value now includes the kustomize version name.
Thank you for addressing this problem so quickly (presumably by way of kubernetes-sigs/kustomize#5644).
What happened?
For kustomizations that opt to include the "app.kubernetes.io/managed-by" label by way of the following stanza,
kustomize does inject the label, but its value no longer mentions the actual kustomize version name. Instead, the label's value winds up "kustomize-unknown".
This appears to be a problem with how we capture the version name and stamp it into the program for use with this lable.
What did you expect to happen?
The resulting manifests should include a member in the "metadata.labels" field named "app.kubernetes.io/managed-by" with a value such as "kustomize-v5.4.0".
How can we reproduce it (as minimally and precisely as possible)?
kustomization.yaml file
```yaml apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization configMapGenerator: - name: example literals: - one=uno - two=dos buildMetadata: - managedByLabel ```Expected output
Actual output
Kustomize version
5.4.0
Operating system
MacOS