Feature Request: Add `kustomize --version` and `kubectl kustomize --version`

Question

Feature Request: Add `kustomize --version` and `kubectl kustomize --version`

SleepyBrett opened this issue 5 years ago · 33 comments

I just spent way to long trying to figure out why the examples in your repo don't work with kubectl kustomize. After finding a rejected MR trying to fix an example I determined that the resources: feature works the way that the examples show only in some versions of kustomize but it took me a while to find in the readme what version of kustomize is included in kubectl.

Alternatively if the flag is hard for whatever reason (I imagine the embedding in kubectl may cause some complication) perhaps the kustomize help screen could include the version number.

der-ali commented 4 years ago

+1

👎3

eddiezane commented 3 years ago

/cc

Answer 1 · 2019-08-01T23:51:10.000Z

Add kustomize --version

For the independent kustomize tool version information is exposed via kustomize version in a format similar to kubectl version

For example:

$ kustomize version
Version: {KustomizeVersion:3.1.0 GitCommit:95f3303493fdea243ae83b767978092396169baf BuildDate:2019-07-26T18:11:16Z GoOs:darwin GoArch:amd64}

and kubectl kustomize --version

This would be a change in the kustomize sub-command in kubectl and so needs to be tracked in kubernetes/kubectl. Having this has come up on slack a few times and you're not the first to open a related issue (#1267) so a feature request there would be welcome.

I just spent way to long trying to figure out why the examples in your repo don't work with kubectl kustomize.

Having more a prominent call out in the README for information relating to the kubectl integration and where to go for examples/docs specific to that would definitely help prevent others running into this as well.

For example these references:

Answer 2 · 2019-10-31T00:02:28.000Z

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

Answer 3 · 2019-11-22T20:58:50.000Z

/remove-lifecycle stale

Answer 4 · 2019-12-10T18:50:00.000Z

Currently, the kustomize version bundled with kubectl is 2.0.3.

For better or worse, this is the second hit for me on google when I search for kubectl kustomize version. So, I'm trying to be helpful for future visitors.

I'm not sure if its possible to check on the command line, but there is currently a note on the README page in this repo that says which versions are included in kubectl:
https://github.com/kubernetes-sigs/kustomize#kubectl-integration

Answer 5 · 2020-03-09T19:06:29.000Z

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

Answer 6 · 2020-03-09T22:09:47.000Z

/remove-lifecycle stale

Answer 7 · 2020-04-19T20:04:18.000Z

And now the table in the kustomize README is out of date: kubectl 1.18.x has been out for about a month. I have no idea if it's still stuck at kustomize 2.0.3. That's probably the safest guess.

Answer 8 · 2020-04-20T13:10:04.000Z

Probably I had problem when using patch command...

Answer 9 · 2020-05-05T23:40:41.000Z

Hello
What version of kustomize is included in kubectl 1.18.2 ?

Answer 10 · 2020-06-08T14:47:11.000Z

I was searching also for the current version of kustomize.
It is still

{
"ImportPath": "sigs.k8s.io/kustomize",
"Rev": "v2.0.3"
},

You can find this on https://github.com/kubernetes/kubectl/blob/v0.18.3/Godeps/Godeps.json

Answer 11 · 2020-06-10T04:06:57.000Z

As a new kustomize user this was definitely confusing. The jump from 2.x to 3.x is important to be aware of.

Answer 12 · 2020-08-04T13:58:55.000Z

Just for anyone still getting caught out by this, judging by related issues of #1500, I think there may be on-going work in #2668 and #2675 that is going to progress this.

Answer 13 · 2020-08-21T16:49:52.000Z

Is the integration with kubectl no longer maintained? It seems unclear what the status of that is based on the version drift that is occurring.

Answer 14 · 2020-11-19T17:32:24.000Z

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

Answer 15 · 2020-11-19T17:44:14.000Z

/remove-lifecycle stale

Answer 16 · 2020-11-19T18:06:07.000Z

We cannot work on this before we re-integrate the kustomize with kubectl. The re-integration is covered by #1500 and #2506

Answer 17 · 2021-02-17T18:46:00.000Z

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-contributor-experience at kubernetes/community.
/lifecycle stale

Answer 18 · 2021-02-17T19:38:16.000Z

/remove-lifecycle stale

Answer 19 · 2021-05-26T00:51:11.000Z

Now that we've also updated to Go 1.16, I think embed could be used as part of the solution here.

cc @jeremyrickard

Answer 20 · 2021-06-08T07:34:53.000Z

apparently, kubectl v1.21 is out now.. has anything changed?
The kustomize FAQ page says that the version should be updated in ~v1.20 https://kubectl.docs.kubernetes.io/faq/kustomize/
If it has changed, it'd be great if the readme.md was updated accordingly.

Answer 21 · 2021-06-15T23:30:22.000Z

Yes, it was updated in 1.21: https://github.com/kubernetes/kubernetes/blob/4d75a6238a6e330337526e0513e67d02b1940b63/CHANGELOG/CHANGELOG-1.21.md#kustomize-updates-in-kubectl

Yes, both the readme and docs need to be updated

Answer 22 · 2021-06-22T15:45:14.000Z

If anyone is wondering about their ubuntu package version I think the ubuntu package might be a bit broken...

~) $ kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.2", GitCommit:"092fbfbf53427de67cac1e9fa54aaa09a28371d7", GitTreeState:"clean", BuildDate:"2021-06-16T12:59:11Z", GoVersion:"go1.16.5", Compiler:"gc", Platform:"linux/amd64"}

~) $ kubectl kustomize version
Error: evalsymlink failure on 'version' : lstat /home/myself/version: no such file or directory

^ I don't think that is correct ...

~) $ kubectl kustomize --version
Error: unknown flag: --version
See 'kubectl kustomize --help' for usage.

~) $ dpkg -l | grep kubectl
ii  kubectl                                    1.21.2-00                                        amd64        Kubernetes Command Line Tool

kubectl |  1.21.2-00 | http://apt.kubernetes.io kubernetes-xenial/main amd64 Packages

Answer 23 · 2021-06-22T15:51:57.000Z

@diclophis that's because no such version command exists, neither as a subcommand nor a flag. That's what this issue is tracking. In kubectl kustomize version, "version" is being interpreted as a path.

Answer 24 · 2021-06-22T15:59:40.000Z

/assign @jeremyrickard

Answer 25 · 2021-07-26T19:54:52.000Z

Workaround? How can we check what version of kustomize kubectl is using?

Answer 26 · 2021-07-26T20:24:34.000Z

For now you'll have to check the Kustomize readme:

https://github.com/kubernetes-sigs/kustomize#kubectl-integration

Answer 27 · 2021-10-24T20:31:47.000Z

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

Answer 28 · 2021-10-25T09:32:51.000Z

@jeremyrickard any news?

Answer 29 · 2022-01-23T09:56:42.000Z

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

Answer 30 · 2022-01-24T08:00:03.000Z

@jeremyrickard could you please take a look?

Answer 31 · 2022-01-24T13:42:44.000Z

Strange, also have this problem on Ubuntu, that Kustomize version is old even though I have kubectl 1.23:

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.2", GitCommit:"9d142434e3af351a628bffee3939e64c681afa4d", GitTreeState:"clean", BuildDate:"2022-01-21T02:20:54Z", GoVersion:"go1.17.6", Compiler:"gc", Platform:"linux/amd64"}

$ kubectl kustomize edit set image foo=bar:0.0.1
error: specify one path to kustomization.yaml

This command should be working in newer kustomize. Another thing, I also think it's rather strange that such basic functionality as being able to check the version of component is unavailable for such long time.