kubectl kustomize versioning

[nicks]

Expected behavior:

kubectl kustomize version

should print information about the version of Kustomize templates that kubectl kustomize accepts

Actual behavior

kubectl kustomize version

doesn't work.

The kubectl command only accepts kustomize version 2+, but the main kustomize repo is on version 3+. This has caused some confusion for our users, because they thought that they should be using the "new way" of preferring kubectl kustomize over kustomize

Obviously, we could work around this by keeping a map from kubectl versions to compatible kustomize versions, but it would be nice if we could get this info from kubectl kustomize

Relatedly, what's the plan for upgrading kubectl to kustomize 3?

[dlipovetsky]

/cc @kubernetes/sig-cli-feature-requests

[dlipovetsky]

Regardless of the future of kubectl kustomize, it would help to know which kustomize version is used.

[ricochet]

Please close and reopen this on kustomize.

[nicks]

great filed as kubernetes-sigs/kustomize#2142.

though i think the change has to happen in this repo, since it's about what subcommands are registered? https://github.com/kubernetes/kubectl/blob/master/pkg/cmd/kustomize/kustomize.go#L59

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[seans3]

/remove-lifecycle stale

[seans3]

/sig cli
/area kubectl