Re: [kubernetes/kubernetes] kubectl version output isn't human readable (#43750)

[Michail Kargakis]

@kubernetes/sig-cli-misc

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[Michail Kargakis]

Agreed on this one, we should pretty-print this output.

[Shiyang Wang]

@php-coder I would like to change that tomorrow if you are not working on it.

[Vyacheslav Semushin]

@shiywang I'm not working on it, so feel free to provide a PR. But I wouldn't do anything untill we get approval from @kubernetes/sig-cli-misc

[Andy Goldstein]

cc @kubernetes/sig-testing-misc, don't some of the tests rely on this output?

[Joe Finney]

They probably do. There should be a kubectl version -o=json option or something that we can use in test infra.

[Alejandro Escobar]

please have a look at:
#39858
and related issue:
#39427

The above is approved and had an lgtm labeled, but removed by the bot because of testing.

[Shiyang Wang]

@kargakis I think we can close this ?

[Vyacheslav Semushin]

@shiywang I don't see that it was fixed. Does the output of kubectl version was improved?

[Giovanni Tirloni]

@php-coder kubectl now has a --output option which lets you select between YAML or JSON.

However, I believe this is reversed. The more human-friendly output is hidden behind an option and the machine-friendly output is the default. I believe it should be the opposite.

[Kubernetes Submit Queue]

Closed #43750 via #46598.

[Culip]

I agree, that minor feature would be great. An obvious workaround is to use kubectl version | tr ',' '\n'. You can also make an alias for your shells.

—
You are receiving this because you are on a team that was mentioned.

Reply to this email directly, view it on GitHub, or unsubscribe.