[KEP-3352] docs for aggregated discovery

[Jefftree]

kubernetes/enhancements#3352

[netlify]

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

Name	Link
🔨 Latest commit	2d9b1a4
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/6602b9f04740f800092d600d

[dipesh-rawat]

/retitle [WIP] [KEP-3352] docs for aggregated discovery

[fsmunoz]

Hello @Jefftree 👋 !

Please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before the deadline Tuesday March 12th 2024 18:00 PST.

Thank you!

[katcosgrove]

Hey @Jefftree! Just a reminder that this needs to be reviewed and ready to merge by Docs Freeze on March 26, including a technical review. An exception request will be required if you cannot meet that deadline. Thank you!

cc: @jpbetz @lavalamp @deads2k

[drewhagen]

@kubernetes/sig-docs-en-owners Can we get an LGTM from docs on this one? The deadline is March 26th 2024 18:00 PT to get this into the release. Thanks!

[drewhagen]

/milestone 1.30
/sig api-machinery

[jpbetz]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 1d859a4582b48b27864f159fdde36cd28bb299a5

[Jefftree]

/assign @sftim

[sftim]

Once this PR has been reviewed and has the lgtm label, please assign divya-mohan0209 for approval. For more information see the Kubernetes Code Review Process.

I'm short on spare capacity to review at the moment.

/unassign
/assign @divya-mohan0209
(but: it is KubeCon week; reviews in general might not be as prompt as is typical)

@divya-mohan0209 is a very capable reviewer and I am more than happy to allow the auto-assignment of Divya as reviewer to stand. Any other approver is welcome to provide approval, and I'll leave this on my long list of things to check back on.

[drewhagen]

I'm reaching out from the Docs team. Just checking in as we approach Docs Freeze on Tuesday March 26th 18:00 PDT. This documentation appears to still be under review. To meet the Docs Freeze, this PR must have a technical review as well as lgtm and approve labels applied, without any unaddressed comments or concerns from SIG Docs. The status of this enhancement is marked as at risk for docs freeze.

Thanks!

[sftim]

Thanks.

Here's some feedback. Now this is graduating to GA, we might need to clarify something around having two headings that have the same text.

[fsmunoz]

@Jefftree hello, Release Lead Shadow for 1.30, acting as Docs shadow here; as @drewhagen mentioned above, the Docs Freeze is fast approaching (Tuesday March 26th 18:00 PDT).

From what I've seen, the technical review is still needed (cc @jpbetz @lavalamp @deads2k , could you take a look?)

There are also some pending comments from SIG Docs - could you take a look? I think that with that (technical + Docs) the lgtm and approve process can follow, and hopefully before the freeze deadline. Thanks!

[jpbetz]

This one looked good to me last pass.

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 1025272c99f9d8521e0cbb806995143644c6da3e

[drewhagen]

Just a heads up that Doc Freeze is approaching fast tomorrow March 26th at 18:00 PDT and starting this cycle, we need to file an Exception after this time.
This one looks pretty close and we'd like to help you get it over the finish line!

@kubernetes/sig-docs-en-owners Does this one look good for an approve from y'all? Thanks!

[sftim]

I committed the one required fix.

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: fe7cc19f7dcba3f445966f185aa890337bc3b699

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jpbetz, sftim

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• content/en/OWNERS [sftim]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[drewhagen]

/milestone 1.30