whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
joshmsamuels
2019-09-12 12:22:28 -04:00
committed by Kubernetes Prow Robot
parent 0c960735a3
commit 809a957294
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/reference/using-api/api-concepts.md
+1 -1
View File
@@ -475,7 +475,7 @@ a little differently.
For instance, only the apply operation fails on conflicts while update does For instance, only the apply operation fails on conflicts while update does
not. Also, apply operations are required to identify themselves by providing a not. Also, apply operations are required to identify themselves by providing a
`fieldManager` query parameter, while the query parameter is optional for update `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: An example object with multiple managers could look like this: