add ContainerRuntimeVersion to kubectl get nodes -o=wide output

[evie404]

What this PR does / why we need it: adds container runtime version to kubectl get nodes -o=wide output as a way to surface more node-level information

When upgrading to a new container runtime version (docker 1.11 -> docker 1.12) or when experimenting with a different container runtime version (experimenting with rkt in a docker cluster), it's useful for cluster operators to see which nodes are running which container runtime version. kubectl get nodes -o=wide already provides kernel and OS version, and I believe adding container runtime version would be good.

Release note:

container runtime version has been added to the output of `kubectl get nodes -o=wide` as `CONTAINER-RUNTIME`

[k8s-ci-robot]

Hi @rickypai. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with @k8s-bot ok to test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[eparis]

@k8s-bot ok to test
@fabiand do we have any thoughts on how wide is too -o wide?

I like it, more than I care about the kernel I usually care about the runtime...

[evie404]

let me give a sample output:

NAME                             STATUS                     AGE       VERSION   EXTERNAL-IP      OS-IMAGE             KERNEL-VERSION       CONTAINER-RUNTIME
ip-10-22-168-211.ec2.internal    Ready                      73d       v1.6.4    24.111.11.60     Ubuntu 14.04.5 LTS   4.4.0-38-generic     docker://1.11.2
ip-10-22-192-121.ec2.internal    Ready                      73d       v1.6.4    34.211.73.26     Ubuntu 14.04.5 LTS   4.4.0-38-generic     docker://1.11.2
ip-10-22-218-12.ec2.internal     Ready                      73d       v1.6.4    56.205.162.20    Ubuntu 14.04.5 LTS   4.4.0-38-generic     docker://1.11.2
ip-10-122-222-121.ec2.internal   Ready                      73d       v1.6.4    84.173.159.122   Ubuntu 14.04.5 LTS   4.4.0-38-generic     docker://1.11.2

in my case, this change makes the line length 156 characters for the title, and 154 characters for the information.
vs. currently: 132 characters for the title, and 134 characters for the node information.

[evie404]

@k8s-bot pull-kubernetes-unit test this

[fabiand]

I guess the question was for @fabianofranz

[evie404]

@k8s-bot pull-kubernetes-federation-e2e-gce test this

[fejta]

@k8s-bot pull-kubernetes-federation-e2e-gce test this
ref: #46827

[evie404]

if I can get some eyes on this that'd be great. @kubernetes/sig-cli-pr-reviews

[k8s-ci-robot]

@rickypai: Reiterating the mentions to trigger a notification:
@kubernetes/sig-cli-pr-reviews.

In response to this:

if I can get some eyes on this that'd be great. @kubernetes/sig-cli-pr-reviews

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[fabianofranz]

Thanks @rickypai!
There isn't a specifically set restriction on -o wide, if you request it you know it can potentially break line.
/lgtm
/approve no-issue
/kind enhancement

[k8s-github-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabianofranz, rickypai

Associated issue requirement bypassed by: fabianofranz

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

• pkg/printers/OWNERS [fabianofranz]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[evie404]

can this be added to 1.7 milestone or wait for 1.8?

[evie404]

/test pull-kubernetes-federation-e2e-gce

[k8s-github-robot]

Automatic merge from submit-queue (batch tested with PRs 47403, 46646, 46906, 46527, 46792)