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.
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
1.18 Server-side apply #19286
1.18 Server-side apply #19286
Conversation
Deploy preview for kubernetes-io-vnext-staging processing. Building with commit 0efc46e https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/5e6beef2a4626b000a57c0d8 |
👋 Please rebase this PR on Feel free to /hold |
Hi, @apelisse today is the deadline for docs placeholder PR to be ready for review state. I see the status of the doc as still TODO Can I know by when can I expect all the docs to be ready for review state? |
/lgtm |
@sftim do you have any comments on these docs? I see a technical |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some feedback
@@ -515,6 +517,9 @@ content type `application/apply-patch+yaml`) and `Update` (all other operations | |||
which modify the object). Both operations update the `managedFields`, but behave | |||
a little differently. | |||
|
|||
{{< note >}}The apply content type `application/apply-patch+yaml` accepts both yaml **and** json, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit:
{{< note >}}The apply content type `application/apply-patch+yaml` accepts both yaml **and** json, | |
{{< note >}}The apply content type `application/apply-patch+yaml` accepts both YAML **and** JSON, |
or, better, reword:
{{< note >}}
Whether you are submitting JSON data or YAML data, use `application/apply-patch+yaml` as the
Content-Type header value.
All JSON documents are valid YAML.
{{< /note >}}
### Known Issues | ||
|
||
- There is a known issue with using Server Side Apply on sub-resource endpoints | ||
where field ownership is not being updated [#88981](https://github.com/kubernetes/kubernetes/issues/88981). | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
### Known Issues | |
- There is a known issue with using Server Side Apply on sub-resource endpoints | |
where field ownership is not being updated [#88981](https://github.com/kubernetes/kubernetes/issues/88981). | |
{{< caution >}} | |
Server Side Apply does not correctly track ownership on sub-resources. If you are using | |
Server Side Apply with a subresource, … | |
{{< /caution >}} |
what should the …
say?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(written to avoid statements about the future)
Apply can send partially specified objects to this endpoint. An applied config | ||
should always include every field that the applier has an opinion about. | ||
Apply can send partially specified objects as yaml or json to this endpoint. | ||
An applied config should always include every field that the applier has an opinion about. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you reword? A reader might think that the applier is the API server; as a piece of code, API servers don't have opinions.
Co-Authored-By: Tim Bannister <tim@scalefactory.com>
@sftim Tentatively improved based on your feedback, possibly made it worse, let me know ;-) Thanks! |
@sftim Can you have a final look here? |
If you rebased @apelisse then you should /hold cancel |
/hold cancel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These changes
/lgtm
(and they seem simple enough not to need detailed tech review etc)
Who's supposed to give the approval? |
SIG Docs release team can approve. @VineethReddy02 are you able to take a look? |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kwiesmueller, VineethReddy02 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This is not empty now.