-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Various Server-Side Apply improvements #36293
Various Server-Side Apply improvements #36293
Conversation
Ah! you've created a |
Reference: kptdev/kpt#3497 (comment) |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
If any of #31261 is useful, feel free to borrow from that PR. |
Also, I don't think this repo has a |
Yeah, not sure why I ended-up having a master branch on my remote that doesn't match the main branch. Also, I love your other PR, but it's fairly big and I'm afraid trying to do too much (merging the two) would significantly delay that quick fix here. |
What I mean is, you can borrow a paragraph or so if that helps you @apelisse - not a merge of all the work so far. No problem with you borrowing sentences or paragraphs; I wouldn't object to a |
Yeah, but I'm afraid that's going to take me a lot of time and possible push-back that I don't really have time to afford right now :-) |
c99d63f
to
c2b1f31
Compare
OK Fixed conflicts. @sftim, I'll see if I can take some of your PR changes into another smaller PR later if you don't mind. |
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.
Found one "Server-Side" you missed. Otherwise lgtm.
@@ -465,12 +465,18 @@ kubectl apply --server-side --field-manager=my-manager [--dry-run=server] | |||
|
|||
## API Endpoint | |||
|
|||
With the Server Side Apply feature enabled, the `PATCH` endpoint accepts the | |||
With the Server-Side Apply feature enabled, the `PATCH` endpoint accepts the | |||
additional `application/apply-patch+yaml` content type. Users of Server Side |
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.
additional `application/apply-patch+yaml` content type. Users of Server Side | |
additional `application/apply-patch+yaml` content type. Users of Server-Side |
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.
nice catch, my very simple search-and-replace didn't catch this case ;-)
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.
Actually I found another instance!
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.
Nice. That is one reason I like to start and end each sentence on its own line. One's searches are not foiled by the end of a line.
c2b1f31
to
746b735
Compare
I improved the regex and even found a few more. |
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.
Seems reasonable.
In addition, I think the first two commits (remove & add section) should be squash into one. How do you think?
Apply can send partially specified objects as YAML to this endpoint. When | ||
applying a configuration, one should always include all the fields that they | ||
have an opinion about. | ||
|
||
### RBAC And permissions |
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.
### RBAC And permissions | |
### RBAC and Permissions |
or
### RBAC And permissions | |
### RBAC and permissions |
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.
@apelisse , What do you think about the second suggestion?
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.
Thanks for the ping, missed that somehow, sending a fix with the second suggestion!
@apelisse , Can you rebase into a single commit? |
LGTM label has been added. Git tree hash: d4619db0cca5c297d358de85414b4a05d94f4ea3
|
/label tide/merge-method-squash |
746b735
to
cae95ce
Compare
Updated |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kbhawkey 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 |
/lgtm |
LGTM label has been added. Git tree hash: 116ad6524ec5024ed7f2d47d1691041cc5ea8289
|
* Remove obsolete caution block for ssa-ing sub-resources * ssa: Add RBAC/Permissions section * ssa: Make everything consistent into "Server-Side Apply"
@justinsb told me he wasn't sure what permissions were needed to use server-side apply, and we're not doing a great job explaining this today so I added that sub-section about it. I think that's the right location since we also explain that ssa is a patch at that location. I also noticed a caution block that is obsolete since GA. And while I was editing this file, I just normalized every instances to
Server-Side Apply
.