Document supported component skew

[janetkuo]

This is a...

• Feature Request
• Bug Report

Problem:
Forked from kubernetes/kubernetes#33212

Kubernetes only allows 2 minor version skew between nodes and master, and 1 minor version skew between kubectl and master. However, this is not mentioned anywhere in user-facing documents. This caused user confusion and may cause unexpected issues to users' clusters.

It's documented in contributors' doc: https://github.com/kubernetes/community/blob/master/contributors/design-proposals/release/versioning.md#supported-releases-and-component-skew

Different components are expected to be compatible across different amounts of skew, all relative to the master version. Nodes may lag masters components by up to two minor versions but should be at a version no newer than the master; a client should be skewed no more than one minor version from the master, but may lead the master by up to one minor version. For example, a v1.3 master should work with v1.1, v1.2, and v1.3 nodes, and should work with v1.2, v1.3, and v1.4 clients.

Proposed Solution:
Add some document(s) in http://kubernetes.io/ to include the above information.

Page to Update:
http://kubernetes.io/...

[zacharysarah]

@janetkuo 👋 Thanks, this is helpful!

[pgadige]

I'm working on this.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten