Kustomize Version Output

[jmcudd]

There is no way of determining the version of kustomize. This is important when debugging issues with kustomize and consulting the kustomize documentation.

Version

4.7.19

Steps To Reproduce

1. oc kustomize --version

Current Result

Error: unknown flag: --version
See 'oc kustomize --help' for usage.

Expected Result

{Version:4.4.0 GitCommit:$Format:%H$ BuildDate:2021-09-29T10:27:55Z GoOs:linux GoArch:amd64}

Additional Information

The catalyst for this issue was seeing differences in behaviour between kubectl apply -k and oc apply -k which lead me to look into which versions of kustomize each CLI is using.

Related issues:

kubernetes/kubectl#797
kubernetes-sigs/kustomize#1424

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dariusdev]

/reopen

it is not resolved yet

[openshift-ci]

@dariusdev: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

it is not resolved yet

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.