### What happened?

Someone opened #124533 saying

> I expected 1.29 libraries to still be compatible with Kubernetes 1.28 based on the kube-apiserver version skew.

I think that is not what the version skew policy (https://kubernetes.io/releases/version-skew-policy/) is trying to say. I think that the guiding principle is that you must first upgrade the servers that store objects of a given API group and resource/kind, then upgrade the clients of those servers.

In particular, the existing version skew policy document explicitly discusses several kinds of components, but does not mention aggregated apiservers. I think that these should be explicitly mentioned.

### What did you expect to happen?

Everybody agrees on what to expect.

### How can we reproduce it (as minimally and precisely as possible)?

Read the cited doc and Issue.

### Anything else we need to know?

Nope

### Kubernetes version

<details>

All of them.

</details>


### Cloud provider

<details>
N/A
</details>


### OS version

<details>

N/A

</details>


### Install tools

<details>
N/A
</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>

The Version Skew Policy does not mention aggregated apiservers
This is a GitHub Issue
repo:kubernetes
owner:kubernetes
Title : The Version Skew Policy does not mention aggregated apiservers
Issue date:

--- start body ---
### What happened?

Someone opened #124533 saying

> I expected 1.29 libraries to still be compatible with Kubernetes 1.28 based on the kube-apiserver version skew.

I think that is not what the version skew policy (https://kubernetes.io/releases/version-skew-policy/) is trying to say. I think that the guiding principle is that you must first upgrade the servers that store objects of a given API group and resource/kind, then upgrade the clients of those servers.

In particular, the existing version skew policy document explicitly discusses several kinds of components, but does not mention aggregated apiservers. I think that these should be explicitly mentioned.

### What did you expect to happen?

Everybody agrees on what to expect.

### How can we reproduce it (as minimally and precisely as possible)?

Read the cited doc and Issue.

### Anything else we need to know?

Nope

### Kubernetes version

<details>

All of them.

</details>


### Cloud provider

<details>
N/A
</details>


### OS version

<details>

N/A

</details>


### Install tools

<details>
N/A
</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>

--- end body ---
