Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update server-side-apply.md #43814

Merged
merged 1 commit into from
Nov 4, 2023
Merged

Update server-side-apply.md #43814

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 0 additions & 11 deletions content/en/docs/reference/using-api/server-side-apply.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -214,17 +214,6 @@ Here's an example of a Server-Side Apply message body (fully specified intent):
of a **patch** request to a valid `v1/configmaps` resource, and with the
appropriate request `Content-Type`).

## Server-Side Apply for custom resources {#custom-resources}

By default, Server-Side Apply treats
{{< glossary_tooltip term_id="CustomResourceDefinition" text="custom resources" >}}
as unstructured data. All keys are treated the same as if they were struct fields for
a built-in API, and all lists are considered atomic.

If the CustomResourceDefinition defines a
[schema](/docs/reference/kubernetes-api/extend-resources/custom-resource-definition-v1/#JSONSchemaProps)
that contains annotations as defined in [Merge strategy](#merge-strategy),
then these annotations will be used when merging objects of this type.

## Operations in scope for field management {#apply-and-update}

Expand Down