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.

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

Merged
merged 3 commits into from Mar 18, 2020
Merged

1.18 Server-side apply #19286

merged 3 commits into from Mar 18, 2020

Conversation

apelisse
Copy link
Member

@apelisse apelisse commented Feb 24, 2020

This is not empty now.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Feb 24, 2020
@k8sio-netlify-preview-bot
Copy link
Collaborator

Deploy preview for kubernetes-io-vnext-staging processing.

Building with commit 0efc46e

https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/5e6beef2a4626b000a57c0d8

@k8s-ci-robot k8s-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 24, 2020
@VineethReddy02
Copy link
Contributor

👋 Please rebase this PR on dev-1.18 in order to avoid merge conflicts.

Feel free to /hold cancel after you've rebased.

/hold

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 7, 2020
@VineethReddy02
Copy link
Contributor

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?

@apelisse
Copy link
Member Author

apelisse commented Mar 9, 2020

cc @kwiesmueller

@apelisse apelisse closed this Mar 9, 2020
@apelisse apelisse reopened this Mar 9, 2020
@k8s-ci-robot k8s-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Mar 11, 2020
@apelisse apelisse changed the title Placehold for 1.18 Server-side apply 1.18 Server-side apply Mar 11, 2020
@apelisse
Copy link
Member Author

cc @VineethReddy02

@k8s-ci-robot k8s-ci-robot added language/en Issues or PRs related to English language sig/docs Categorizes an issue or PR as relevant to SIG Docs. and removed approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 11, 2020
@kwiesmueller
Copy link
Member

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 13, 2020
@VineethReddy02
Copy link
Contributor

@sftim do you have any comments on these docs? I see a technical lgtm
If you are okay, I can go ahead with my approval.

Copy link
Contributor

@sftim sftim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some feedback

content/en/docs/reference/using-api/api-concepts.md Outdated Show resolved Hide resolved
@@ -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,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit:

Suggested change
{{< 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 >}}

content/en/docs/reference/using-api/api-concepts.md Outdated Show resolved Hide resolved
Comment on lines 669 to 680
### 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).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### 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?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link
Contributor

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.

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 13, 2020
@apelisse
Copy link
Member Author

@sftim Tentatively improved based on your feedback, possibly made it worse, let me know ;-) Thanks!

@VineethReddy02
Copy link
Contributor

@sftim Can you have a final look here?

@sftim
Copy link
Contributor

sftim commented Mar 17, 2020

If you rebased @apelisse then you should /hold cancel
See #19286 (comment)

@apelisse
Copy link
Member Author

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 17, 2020
Copy link
Contributor

@sftim sftim left a 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)

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 17, 2020
@apelisse
Copy link
Member Author

Who's supposed to give the approval?

@sftim
Copy link
Contributor

sftim commented Mar 17, 2020

SIG Docs release team can approve. @VineethReddy02 are you able to take a look?

@VineethReddy02
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 18, 2020
@k8s-ci-robot k8s-ci-robot merged commit ed434a8 into kubernetes:dev-1.18 Mar 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. language/en Issues or PRs related to English language lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/docs Categorizes an issue or PR as relevant to SIG Docs. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants