Value of the "app.kubernetes.io/managed-by" field no longer mentions actual version

[seh]

What happened?

For kustomizations that opt to include the "app.kubernetes.io/managed-by" label by way of the following stanza,

buildMetadata:
- managedByLabel

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

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

configMapGenerator:
- name: example
  literals:
  - one=uno
  - two=dos

buildMetadata:
- managedByLabel

Expected output

apiVersion: v1
data:
  one: uno
  two: dos
kind: ConfigMap
metadata:
  labels:
    app.kubernetes.io/managed-by: kustomize-5.4.0
  name: example-t85cb8kk54

Actual output

apiVersion: v1
data:
  one: uno
  two: dos
kind: ConfigMap
metadata:
  labels:
    app.kubernetes.io/managed-by: kustomize-unknown
  name: example-t85cb8kk54

Kustomize version

5.4.0

Operating system

MacOS

[jefferybradberry]

It also shows this way:

$ kustomize version
unknown

[stormqueen1990]

/triage accepted
/kind bug

[stormqueen1990]

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?

[seh]

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 #5644).