Server-side Apply

[apelisse]

Feature Description

• One-line feature description (can be used as a release note): Move "apply" and declarative object management from kubectl to the apiserver in order to fix many of the existing bugs that we can't fix today. Also use that opportunity to add "field ownership".
• Primary contact (assignee): @apelisse @lavalamp
• Responsible SIGs: sig-api-machinery sig-cli (wg-apply was created for that purpose).
• Design proposal link (community repo): https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/555-server-side-apply
• Link to e2e and/or unit tests:
  • Unit-tests:
    • https://github.com/kubernetes-sigs/structured-merge-diff/blob/master/typed/merge_test.go
    • https://github.com/kubernetes-sigs/structured-merge-diff/blob/master/typed/deduced_test.go
    • https://github.com/kubernetes-sigs/structured-merge-diff/blob/master/typed/symdiff_test.go
    • https://github.com/kubernetes-sigs/structured-merge-diff/blob/master/typed/toset_test.go
    • https://github.com/kubernetes-sigs/structured-merge-diff/blob/master/typed/validate_test.go
    • https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/endpoints/handlers/fieldmanager/fieldmanager_test.go
  • Integration tests:
    • https://github.com/kubernetes/kubernetes/blob/master/test/cmd/apply.sh
    • https://github.com/kubernetes/kubernetes/blob/master/test/integration/apiserver/apply/apply_test.go
    • https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiextensions-apiserver/test/integration/apply_test.go
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @lavalamp @pwittrock @erictune
• Approver (likely from SIG/area to which feature belongs): @bgrant0607
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y) 1.14
  • Beta release target (x.y) 1.15
  • Stable release target (x.y) 1.21

[idvoretskyi]

/assign @apelisse

[zparnold]

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!!!!!

[justaugustus]

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

[apelisse]

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