Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update 1.11 --server-print info #8870

Merged
merged 2 commits into from
Jun 1, 2018
Merged

update 1.11 --server-print info #8870

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0aff9f3
update 1.11 --server-print info
juanvallejo Jun 1, 2018
8537e3d
Copyedit
Jun 1, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions content/en/docs/reference/kubectl/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -203,15 +203,18 @@ submit-queue 610995
This means that for any given resource, the server will return columns and rows relevant to that resource, for the client to print.
This allows for consistent human-readable output across clients used against the same cluster, by having the server encapsulate the details of printing.

To output object information using this feature, you can add the `--experimental-server-print` flag to a supported `kubectl` command.
This feature is enabled by default in `kubectl` 1.11 and higher. To disable it, add the
`--server-print=false` flag to the `kubectl get` command.

##### Examples

To print information about the status of a pod, use a command like the following:

```shell
$ kubectl get pods <pod-name> --experimental-server-print
kubectl get pods <pod-name> --server-print=false
```

The result of running this command is:
Output looks like this:

```shell
NAME READY STATUS RESTARTS AGE
Expand Down