Please fill in the following information:

Issue description:

The above section contains the following:

With client-side apply, commands such as kubectl apply submit the full definition of a resource to the API server. The API server overwrites the entire resource with the submitted definition.

With server-side apply, API clients submit partial resource definitions, and the API server updates only the submitted parts. Then, your application definitions can include only your changes and exclude parts of the resource that you do not want to manage.

This is not correct. It's quite the other way round: server-side-apply transfers the complete resource and the server decides what to update (it doesn't just overwrite).

With client-side-apply the client checks which changes need to be patched.

Hence the names "server-side" and "client-side"

Steps to reproduce:

Workaround:

Expected result: