Re: Exception / notification about missing docs freeze

[Kat Cosgrove]

As a technical lead for SIG Docs, +1

We apologize for the inconvenience and beg the mercy of the release team.

But also, lol

On Tue, Aug 4, 2026 at 5:10 PM 'Tim Bannister' via release-team <releas...@kubernetes.io> wrote:

Hello folks, 

I want to ask for a special case docs freeze exception for - https://github.com/kubernetes/website/pull/56811

Enhancement name: KYAML

Additional time needed: it's complicated, but basically none

Reason this enhancement is critical for this milestone: feature has been implemented and merged, and other docs are ready. We could revert it, but actually the missing piece is an update to the YAML examples. It's not SIG CLI that needs to act, it is - exceptionally - SIG Docs.

Risks from adding code late: (to k8s stability, testing, etc.) N/A 

Risks from cutting enhancement: no real risk.

Here's what I proposed: fast follow updates. Get everything ready to update the example manifests on https://kubernetes.io to be KYAML, but save the actual update to happen just after the v1.37 release. That's feasible. It keeps the work and the urgency out of the release docs team's efforts, where it doesn't really belong anyway.

I will also start a branch, separate from https://github.com/kubernetes/website/pull/56811, where the real work can live ready for that fast follow. Why a different branch? Well, https://github.com/kubernetes/website/pull/56811 is a sort of marker PR. There's nothing extra to merge in before the v1.37 release, so https://github.com/kubernetes/website/pull/56811 contains nothing.

SIG Docs are happy with that approach; see https://github.com/kubernetes/website/pull/56811#issuecomment-5183507042

However, I want to file this exception request, so that there is something to point at and track.

Tim Bannister

To unsubscribe from this group and stop receiving emails from it, send an email to release-team...@kubernetes.io.

[Tim Bannister]

[Natali Vlatko]

In case another +1 is needed, +1 from me, SIG Docs co-chair (I have also indicated leadership sign-off on the placeholder PR for the release team's information).

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-re...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kubernetes-sig-release/CABHW_BdHZV9n1RXYCyeJunsPRCYwVruk6f6EpPekmxjvWjf5zw%40mail.gmail.com.

[Maciej Szulik]

I'm also supportive from SIG-CLI pov. I'll sync with Tim regarding who will actually make it happen. 

To view this discussion visit https://groups.google.com/d/msgid/kubernetes-sig-release/CA%2BUAEgR3_N%2BFth6tVYAV4Txu1LG_7vJXUOVYV_UR58LyLX_mAw%40mail.gmail.com.

[Benjamin Elder]

Thanks all!

To view this discussion visit https://groups.google.com/d/msgid/kubernetes-sig-release/CALC2N4aQXjXzSnqYrVRAHp%2Bicm-PBmNO6th8qVXqTxW7jNmOrg%40mail.gmail.com.