File tree Expand file tree Collapse file tree 1 file changed +0
-11
lines changed
content/en/docs/reference/using-api Expand file tree Collapse file tree 1 file changed +0
-11
lines changed Original file line number Diff line number Diff line change @@ -214,17 +214,6 @@ Here's an example of a Server-Side Apply message body (fully specified intent):
214
214
of a **patch** request to a valid `v1/configmaps` resource, and with the
215
215
appropriate request `Content-Type`).
216
216
217
- # # Server-Side Apply for custom resources {#custom-resources}
218
-
219
- By default, Server-Side Apply treats
220
- {{< glossary_tooltip term_id="CustomResourceDefinition" text="custom resources" >}}
221
- as unstructured data. All keys are treated the same as if they were struct fields for
222
- a built-in API, and all lists are considered atomic.
223
-
224
- If the CustomResourceDefinition defines a
225
- [schema](/docs/reference/kubernetes-api/extend-resources/custom-resource-definition-v1/#JSONSchemaProps)
226
- that contains annotations as defined in [Merge strategy](#merge-strategy),
227
- then these annotations will be used when merging objects of this type.
228
217
229
218
# # Operations in scope for field management {#apply-and-update}
230
219
You can’t perform that action at this time.
0 commit comments