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

Jump to bottom

Update Skew Docs to Fix Compatible Issues between Controller Clients and the API-Server #46109

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Update Skew Docs to Fix Compatible Issues between Controller Clients and the API-Server #46109

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
50f2276
Update version-skew-policy.md
network-charles May 1, 2024
01bc097
Update version-skew-policy.md
network-charles May 2, 2024
e09bd26
Update version-skew-policy.md
network-charles May 4, 2024
906570d
Fix title
network-charles May 6, 2024
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
6 changes: 6 additions & 0 deletions content/en/releases/version-skew-policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -239,3 +239,9 @@ or **{{< skew currentVersionAddMinor -3 >}}**)
Running a cluster with `kube-proxy` instances that are persistently three minor versions behind
`kube-apiserver` means they must be upgraded before the control plane can be upgraded.
{{</ warning >}}

## Consideration of supported skew for other components

Administrators should consider the supported skew of other components as well when determining compatibility within their cluster.
While each component has a version skew policy, it's essential to ensure that the versions of all components align properly to avoid
disrupting critical operations, especially those related to admission control and flow control.