Aggregated Discovery

[Jefftree]

Enhancement Description

• One-line enhancement description (can be used as a release note): Aggregated Discovery

• Kubernetes Enhancement Proposal: KEP

• Discussion Link:

• Primary contact (assignee): @Jefftree

• Responsible SIGs: SIG API Machinery, SIG CLI

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

  • Alpha release target (x.y): 1.26
  • Beta release target (x.y): 1.27
  • Stable release target (x.y):

• Alpha

  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
    • Aggregated discovery server changes kubernetes#113171
    • Aggregated discovery client kubernetes#113599

• Beta

  • KEP (k/enhancements) update PR(s): KEP-3352 Aggregated Discovery to Beta #3722
  • Code (k/k) update PR(s):
    • Surface "stale" GroupVersions from AggregatedDiscovery kubernetes#116145
    • Enable Aggregated Discovery for Beta kubernetes#116108
    • Fix legacy fallback stale for aggregated discovery kubernetes#115770
    • Add metrics for aggregated discovery kubernetes#115630
  • Docs (k/website) update(s): Doc update for KEP-3352 Aggregated Discovery website#40024

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

[Jefftree]

/sig api-machinery
/sig cli

[Priyankasaggu11929]

/milestone v1.25

[Priyankasaggu11929]

Hello @Jefftree 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 16, 2022.

For note, This enhancement is targeting for stage alpha for 1.25 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP file using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable
• KEP has a updated detailed test plan section filled out
• KEP has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

Looks like for this one, we would just need to get the open KEP PR #3364 merged by the Enhancements Freeze.

For note, the status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[Priyankasaggu11929]

Hello @Jefftree 👋, just a quick check-in again, as we approach the 1.25 enhancements freeze.

Please plan to get the open KEP PR merged before enhancements freeze on Thursday, June 23, 2022 at 18:00 PM PT.

For note, the current status of the enhancement is atat-risk. Thank you!

[Priyankasaggu11929]

With KEP PR #3364 merged now, the enhancement is ready for the upcoming Enhancements Freeze.

For note, the status is now marked as tracked. Thank you so much!

[didicodes]

Hello @Jefftree 👋, 1.25 Release Docs Shadow here.

This enhancement is marked as ‘Needs Docs’ for the 1.25 release. Please follow the steps detailed in the documentation to open a PR against the dev-1.25 branch in the k/website repo. This PR can be just a placeholder at this time and must be created by August 4.


Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release. Thank you!

[Atharva-Shinde]

Hi @Jefftree, Enhancements team here again 👋

Checking in as we approach Code Freeze at 01:00 UTC on Wednesday, 3rd August 2022.

Please ensure that the following items are completed before the code-freeze:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PRs are fully merged by the code freeze deadline.

Currently, the status of the enhancement is marked as at-risk

Thanks :)

[Atharva-Shinde]

Hey @Jefftree , reaching out again as we approach Code Freeze at 01:00 UTC on this Wednesday i.e 3rd August 2022.
Try to get this PR kubernetes/kubernetes#111409 merged and update the Issue Description by adding the PR linked, before the code-freeze :)

The status of the enhancement is still marked as at-risk

[Jefftree]

Hello, we will be dropping this enhancement for 1.25. Thanks!

[Atharva-Shinde]

Thanks for the update @Jefftree ! I have marked this enhancement as Removed from milestone in the tracking sheet.
Clearing the milestone
/milestone clear

[kikisdeliveryservice]

If you're moving forward with this, please update the kep.yaml that just merged as it has milestone 1.25 still :)

[deads2k]

/milestone v1.26
/label lead-opted-in
/label tracked/yes

[k8s-ci-robot]

@deads2k: Can not set label tracked/yes: Must be member in one of these teams: [release-team-enhancements release-team-leads]

In response to this:

/milestone v1.26
/label lead-opted-in
/label tracked/yes

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.

[marosset]

/remove-label lead-opted-in
/remove-label tracked/yes
/label tracked/no
/milestone clear

[deads2k]

/milestone v1.27
/label lead-opted-in
/stage beta

[npolshakova]

Hello @Jefftree 👋, 1.27 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage beta for 1.27 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.27
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is marked as tracked. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[mickeyboxell]

Hi @Jefftree 👋, I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release.

Please feel free to reach out with any questions. Thanks!

[npolshakova]

Hi @Jefftree,

Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.

Please ensure the following items are completed:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PRs are fully merged by the code freeze deadline.

Please let me know if there are any other PRs in k/k I should be tracking for this KEP.
As always, we are here to help should questions come up. Thanks!

[deads2k]

/milestone v1.28
/label lead-opted-in

[deads2k]

Spoke with Jefftree. Letting this soak in beta for another release.

/remove-label lead-opted-in
/milestone clear