order of kubectl upgrade is out of line with the version skew policy

[cbf123]

This is a Bug Report

Problem:

Upgrading Linux nodes | Kubernetes says to upgrade kubectl after upgrading the control-plane (alongside kubelet).

However, if you take advantage of the version skew policy and upgrade the control-plane by 2 or 3 versions without upgrading the worker nodes, this results in kubectl being outside of the +/- 1 version from kube-apiserver allowed by the version skew policy.

Proposed Solution:

kubectl should be upgraded alongside kubeadm, which will keep it within +/- 1 version of kube-apiserver.

Page to Update:
https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/upgrading-linux-nodes/

[kubernetes-prow]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

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-sigs/prow repository.

[cbf123]

/goof-first-issue