Apply for client-go's typed clients

[jpbetz]

Apply for client-go's typed clients

• One-line enhancement description (can be used as a release note): Add typesafe Apply support to client-go's typed clients.

• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/2155-clientgo-apply

• Discussion Link: discussion at kubebuilder/controller-tools meeting, discussion at sig-api-machinery meeting

• Primary contact (assignee): jpbetz@

• Responsible SIGs: sig-api-machinery, wg-api-expression,

• Enhancement target (which target equals to which milestone):

  • As a subproject of Server Side Apply, and as a pre-requisite of Server Side Apply graduating to GA, this enhancement will have the same stability level as Server Side Apply. It will not have a separately tracked stability level. Since Server Side Apply is currently Beta, this enhancement currently focuses on achieving what is required to go to GA.

• Beta

  • KEP (k/enhancements) update PR(s): Provisional KEP: Apply for client-go's typed clients #2156, Apply for client-go's typed clients #2155
  • Code (k/k) update PR(s): Apply Builders for client-go's typed client kubernetes#99012, Add Apply to client-go's typed client kubernetes#99214, Add Extract support to client-go apply builders kubernetes#99759, Migrate cluster role aggregator to apply kubernetes#99462
  • Docs (k/website) update(s): Changes are isolated to client-go, which is not documented on the kubernetes website

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

/sig api-machinery
/wg api-expression
/cc @jennybuckley @apelisse @kwiesmueller @DirectXMan12

[deads2k]

/milestone 1.21
/stage stable

This is a sub-kep of #555

[k8s-ci-robot]

@deads2k: The provided milestone is not valid for this repository. Milestones in this repository: [keps-beta, keps-ga, v1.17, v1.18, v1.19, v1.20, v1.21, v1.22, v1.23]

Use /milestone clear to clear the milestone.

In response to this:

/milestone 1.21
/stage stable

This is a sub-kep of #555

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[deads2k]

/milestone v1.21

[annajung]

Hi @jpbetz

Enhancements Freeze is 2 days away, Feb 9th EOD PST

Enhancements team is aware that KEP update is currently in progress (PR #2419). Please make sure PR merges before the freeze. For PRR related questions or to boost the PR for PRR review, please reach out in slack #prod-readiness

Any enhancements that do not complete the following requirements by the freeze will require an exception.

• [IN PROGRESS] The KEP must be merged in an implementable state
• [DONE] The KEP must have test plans
• [IN PROGRESS] The KEP must have graduation criteria
• [IN PROGRESS] The KEP must have a production readiness review

[jpbetz]

Thanks @annajung The KEP is now merged. The merge includes PRR review and graduation criteria. I'll update this PR description with a link to the merged KEP.

[annajung]

With PR #2419 merged in, this enhancement has met all the criteria for the enhancements freeze 👍

[JamesLaverack]

Hi @jpbetz,

Since your Enhancement is scheduled to be in 1.21, please keep in mind the important upcoming dates:

• Tuesday, March 9th: Week 9 — Code Freeze
• Tuesday, March 16th: Week 10 — Docs Placeholder PR deadline
  • If this enhancement requires new docs or modification to existing docs, please follow the steps in the Open a placeholder PR doc to open a PR against k/website repo.

As a reminder, please link all of your k/k PR(s) and k/website PR(s) to this issue so we can track them.

Thanks!