/assign @apelisse

Looks like we still need some docs to get this feature ready for release @apelisse
Could I please get some help with that? If there’s anything I can do to assist please let me know

At a minimum we're looking to have a placeholder PR on the kubernetes/website repo. The process is fairly straightforward: checkout release-1.11 branch, make a placeholder commit, push it to your fork, and raise a PR between it and the release-1.11 branch, with /hold status.

THANKS SO MUCH!!!!!

@apelisse I noticed the milestone change. Are you planning on pulling this from the 1.11 release?

Yeah, not in 1.11. I'm updating the body.

Thanks @apelisse!

Unsure if it is the right place to comment about this, but we have been working on our own kind of "server side apply" by building https://github.com/seibert-media/dimios
While this is solely a slack time project which we hope to build our future interaction with Kubernetes on, we both stumbled into problems with the entire apply process (discussed on slack with some people) but also did some thinking on how to best approach this.

While I haven't worked on K8s directly myself yet, I could imagine to contribute to this idea/feature if possible/wanted.

Can you send this as an email to kubernetes-wg-apply@googlegroups.com? We can follow-up there.

@apelisse I am not allowed to post messages to said group (kwiesmueller@seibert-media.net)

Sorry, you may need to join the group first: https://groups.google.com/forum/#!forum/kubernetes-wg-apply

Blue button, "Join group to post" (top left)

@apelisse @kubernetes/sig-api-machinery-feature-requests @kubernetes/sig-cli-feature-requests --

This feature was removed from the previous milestone, so we'd like to check in and see if there are any plans for this in Kubernetes 1.12.

If so, please ensure that this issue is up-to-date with ALL of the following information:

• One-line feature description (can be used as a release note):
• Primary contact (assignee):
• Responsible SIGs:
• Design proposal link (community repo):
• Link to e2e and/or unit tests:
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
• Approver (likely from SIG/area to which feature belongs):
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y)
  • Beta release target (x.y)
  • Stable release target (x.y)

Set the following:

• Description
• Assignee(s)
• Labels:
  • stage/{alpha,beta,stable}
  • sig/*
  • kind/feature

Please note that the Features Freeze is July 31st, after which any incomplete Feature issues will require an Exception request to be accepted into the milestone.

In addition, please be aware of the following relevant deadlines:

• Docs deadline (open placeholder PRs): 8/21
• Test case freeze: 8/28

Please make sure all PRs for features have relevant release notes included as well.

Happy shipping!

/cc @justaugustus @kacole2 @robertsandoval @rajendar38

I think everything is there @justaugustus! Thank you

Thanks for the update, @apelisse!

Hey there! @apelisse I'm the wrangler for the Docs this release. Is there any chance I could have you open up a docs PR against the release-1.12 branch as a placeholder? That gives us more confidence in the feature shipping in this release and gives me something to work with when we start doing reviews/edits. Thanks! If this feature does not require docs, could you please update the features tracking spreadsheet to reflect it?

@zparnold Changed the milestone from 1.12 to 1.13 :-). You can forget about this for now, thanks.

After speaking with @apelisse, this enhancement has been deferred and will no longer be tracked for 1.21

We've updated the tracking sheet, can we mark this as a 1.22 milestone? Also, this is code complete already.

@apelisse Of course. Thanks for updating the tracking sheet!

/milestone v1.22

@apelisse - 1.22 enhancements team here! Looks like we're on track for 1.22. I think the only thing would maybe be updating the graduation criteria of the KEP to reference 1.22 rather than 1.21 for GA. Also, if you're able to update the structure of the KEP for the latest template (https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template), that would be awesome. Though, I don't think any of that would be a problem for enhancements freeze on 5/13.

Let us know If there's anything we can do to help!

CC @JamesLaverack

Not super excited to spend some time updating the KEP template now that we're all done with the feature ;-)

Tracking #2732 for the updates. Thanks!

Hello @apelisse 👋, 1.22 Docs release lead here.
This enhancement is marked as ‘Needs Docs’ for 1.22 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.22 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Fri July 9, 11:59 PM PDT.
 Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

p.s.: please don't forget to update the ServerSideApply feature gate in the feature gates table to reflect the graduation.

Thanks, we've already updated most of the documentation in master branch, earlier this cycle. We should be good to go!

p.s.: please don't forget to update the ServerSideApply feature gate in the feature gates table to reflect the graduation.

Done here: kubernetes/website#28038

Hi @apelisse! Checking in from the enhancements team as we're just over 2 weeks away from code freeze. Are there any open or merged k/k PRs we should be tracking for this? Thanks!

Hi @salaxander! To my knowledge there is nothing waiting for the code freeze.
We have some work happening in controller-runtime but that's not affected.
So we should be good for v1.22.

Hey @apelisse and @kwiesmueller - Can you open a PR on the KEP to change to status to implemented? At that point we can close out the issue :)

Thanks!

@salaxander @apelisse Can we close this issue? We're all done here right after 1.22? :D

Yep, sounds good!

3.5 years later ;-)

Could we update this in the description https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/0006-apply.md .. to something that works, please :-) ?

Could we update this in the description https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/0006-apply.md .. to something that works, please :-) ?

Done! Thanks for noticing ;-)

Not sure this is the good place to xreference as the issue is already closed, but potential users of SSA are likely to look here. Cross referencing an open issue for better visibility: kubernetes/kubernetes#113482.

EDIT: opened the PR to update the KEP as well for better visibility: #4308.