Updated docs to document the api change which prevents managed fields during a server-side apply (#16320)

This commit is contained in:
joshmsamuels
2019-09-12 12:22:28 -04:00
committed by Kubernetes Prow Robot
parent 0c960735a3
commit 809a957294
@@ -475,7 +475,7 @@ a little differently.
For instance, only the apply operation fails on conflicts while update does
not. Also, apply operations are required to identify themselves by providing a
`fieldManager` query parameter, while the query parameter is optional for update
operations.
operations. Finally, when using the apply operation you cannot have `managedFields` in the object that is being applied.
An example object with multiple managers could look like this: