![]() Automatic merge from submit-queue kubectl: add less verbose version The kubectl version output is very complex and makes it hard for users and vendors to give actionable information. For example during the recent Kubernetes 1.4.3 TLS security scramble I had to write a one-liner for users to get out the version number to give to figure out if they are vulnerable: ``` $ kubectl version | grep -i Server | sed -n 's%.*GitVersion:"\([^"]*\).*%\1%p' ``` Instead this patch outputs simply output by default ``` ./kubectl version Client Version: v1.4.3 Server Version: v1.4.3 ``` Adding the `--verbose` flag will output the old format. |
||
---|---|---|
.. | ||
admin | ||
api-reference | ||
design | ||
devel | ||
getting-started-guides | ||
images | ||
man/man1 | ||
proposals | ||
user-guide | ||
yaml/kubectl | ||
api.md | ||
OWNERS | ||
README.md | ||
reporting-security-issues.md | ||
roadmap.md | ||
troubleshooting.md | ||
warning.png | ||
whatisk8s.md |
Kubernetes Documentation: releases.k8s.io/HEAD
-
The User's guide is for anyone who wants to run programs and services on an existing Kubernetes cluster.
-
The Cluster Admin's guide is for anyone setting up a Kubernetes cluster or administering it.
-
The Developer guide is for anyone wanting to write programs that access the Kubernetes API, write plugins or extensions, or modify the core code of Kubernetes.
-
The Kubectl Command Line Interface is a detailed reference on the
kubectl
CLI. -
The API object documentation is a detailed description of all fields found in core API objects.
-
An overview of the Design of Kubernetes
-
There are example files and walkthroughs in the examples folder.
-
If something went wrong, see the troubleshooting document for how to debug. You should also check the known issues for the release you're using.
-
To report a security issue, see Reporting a Security Issue.