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): 1.30

• 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

• Stable

  • KEP (k/enhancements) update PR(s): KEP-3352: Aggregated Discovery to GA #4472
  • Code (k/k) update PR(s):
    • Add aggregated discovery v2 types kubernetes#122880
    • Use Aggregated Discovery v2 types and promote to GA kubernetes#122882
    • Aggregated Discovery, mark APIServices stale before initial health check kubernetes#122883
    • e2e for aggregated discovery kubernetes#122977
    • remove unused service keys from aggregated discovery kubernetes#123517
  • Docs (k/website) update(s):
    • [KEP-3352] docs for aggregated discovery website#45267

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!