Statusz for Kubernetes Components

[richabanker]

Enhancement Description

• Introduces a statusz page for all core components.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-instrumentation/4827-component-statusz/README.md
• Discussion Link: link
• Primary contact (assignee): @richabanker
• Responsible SIGs: sig-instrumentation
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.32
  • Beta release target (x.y): 1.33
  • Stable release target (x.y): 1.34
• [ ] Alpha
  • [x] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/4830
  • [ ] Code (k/k) update PR(s):
    • [x] https://github.com/kubernetes/kubernetes/pull/127206
    • [ ] https://github.com/kubernetes/kubernetes/pull/125577
  • [ ] Docs (k/website) update PR(s):

[richabanker]

/assign

[richabanker]

/sig instrumentation

[aojea]

logistic question for sig-instrumentation folks, don't you prefer to consolidate all statusz, flagz and featurez in a single kep to avoid the overhead? or is that there is risk for something to not be graduated at the same time?

[logicalhan]

logistic question for sig-instrumentation folks, don't you prefer to consolidate all statusz, flagz and featurez in a single kep to avoid the overhead? or is that there is risk for something to not be graduated at the same time?

No, some pages may be more contentious than the others. Centralizing z-pages itself has been agreed to be of general benefit to the community (rather than one offs in the kubelet).

[impact-maker]

Hello @richabanker 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

This enhancement is targeting for stage alpha for v1.32 (correct me, if otherwise).

Here's where this enhancement currently stands:

• [x] KEP readme using the latest template has been merged into the k/enhancements repo.
• [x] KEP status is marked as implementable for latest-milestone: v1.32.
• [x] KEP readme has up-to-date graduation criteria
• [ ] KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday, October 3rd, 2024 so that the PRR team has enough time to review your KEP.

For this KEP, we would just need to update the following:

• [ ] KEP has a production readiness review that has been completed and merged into k/enhancements.

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[pacoxu]

/milestone v1.32

[edithturn]

Hello @richabanker , 👋🏼 this is Edith from the v1.32 Communications Team!

We’d love for you to consider writing a feature blog about your enhancement! ✍ Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

To opt-in, let us know and open a Feature Blog placeholder PR against the website repository by 30th Oct 2024 🗓 . For more information about writing a blog, see the blog contribution guidelines.

Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[rdalbuquerque]

Hello @richabanker :wave:, 1.32 Docs Shadow here. Does this enhancement work planned for 1.32 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 2024 18:00 PDT. Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you!

[richabanker]

@rdalbuquerque Created a docs PR here https://github.com/kubernetes/website/pull/48368, thanks!

[richabanker]

@edithturn Created a blog PR here https://github.com/kubernetes/website/pull/48369, thanks!

[tjons]

Hey again @richabanker 👋 v1.32 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 2024 .

Here's where this enhancement currently stands:

• [x] All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• [ ] All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):

• https://github.com/kubernetes/kubernetes/pull/125577

Additionally, please let me know if there are any other PRs in k/k not listed in the description or not linked with this GitHub issue that we should track for this KEP, so that we can maintain accurate status.

The status of this enhancement is marked as at risk for code freeze.

If you anticipate missing code freeze, you can file an exception request in advance. Thank you!

[tjons]

Hello @richabanker 👋, Enhancements team here.

With all the implementation(code related) PRs merged as per the issue description:

• https://github.com/kubernetes/kubernetes/pull/127206
• https://github.com/kubernetes/kubernetes/pull/128196
• https://github.com/kubernetes/kubernetes/pull/125577

This enhancement is now marked as tracked for code freeze for the 1.32 Code Freeze!

Please note that KEPs targeting stable need to have the status field marked as implemented in the kep.yaml file after code PRs are merged and the feature gates are removed.

[rashansmith]

Hello @richabanker 👋, v1.32 Comms team here,

Thank you for creating a placeholder PR for a feature blog!

The deadline for completing blog content to be Ready for Review is Monday 25th November 2024 . For more information about writing a blog see the blog contribution guidelines.

Please feel free to reach out if you have any questions!

[rdalbuquerque]

Hi @richabanker ! Can you please update the docs PR link in the issue description?

Thanks!

[richabanker]

@rdalbuquerque done. Thanks for noticing that!

[dipesh-rawat]

Hello @richabanker 👋, 1.33 Enhancements Lead here.

I’m closing milestone 1.32 now. If you'd like to work on this enhancement in v1.33, please have the SIG lead opt-in by adding the lead-opted-in label, which ensures it gets added to the tracking board. Also, please set the milestone to v1.33 using /milestone v1.33. Thanks!

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

[dashpole]

This will not be moved to beta in 1.33. It will be extended to other components beyond the API Server

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[richabanker]

/remove-lifecycle stale

[richabanker]

/milestone v1.35 /lead-opted-in

[SergeyKanzhelev]

You likely meant

/label lead-opted-in

[raesene]

Hey all, I was just reading this and one thing I wanted to check. From the KEP RBAC is being used to restrict access to the endpoints for all components. AFAIK last time I looked that wasn't possible with kube-proxy and the restriction was done purely on the basis of listening on localhost by default (Which not all distros follow).

Do you know, does the current implementation for kube-proxy have any tie up to an Authentication/Authorization requirement? If that's not going to be implemented, it might be worth flagging in the KEP.

[rayandas]

Hello @richabanker 👋, v1.35 Enhancements team here.

This is a reminder of the upcoming PRR freeze on Thursday 9th October 2025 (AoE) / Friday 10th October 2025, 12:00 UTC.

This enhancement is targeting stage Beta for v1.35 (correct me, if otherwise)

Here's where this enhancement currently stands:

• [x] PR open or merged with the KEP's PRR questionnaire filled out.
• [x] PR open or merged with kep.yaml updated with the stage, latest-milestone, and milestone struct filled out.
• [x] PR open or merged with a PRR approval file with the PRR approver listed for the stage the KEP is targeting.

For this KEP, we would just need to update the following:

• Raise a PR to update the stage, latest-milestone, and milestone struct in the kep.yaml
• Raise a PR to add the PRR approver for the milestone you're targeting this release cycle (which is Beta).

Note that the PRs are not required to be approved or merged by the PRR freeze deadline. Having the PRR questionnaire filled out by the deadline will help ensure that the PRR team has enough time to review your KEP before enhancements freeze on Thursday 16th October 2025 (AoE) / Friday 17th October 2025, 12:00 UTC. For more information on the PRR process, see here.

The status of this enhancement is marked as At risk for PRR freeze. Please keep the issue description up-to-date with appropriate stages as well.

If you anticipate missing PRR freeze, you can file an exception request in advance. Thank you!

[richabanker]

@rayandas PR raised for both pending items in the checklist: https://github.com/kubernetes/enhancements/pull/5611

Thanks to @jpbetz who has has graciously offered to help us out with PRR!

[rayandas]

Hey @richabanker thanks for the PR! You also need to add an approver for Beta in the prod readiness file: https://github.com/kubernetes/enhancements/blob/master/keps/prod-readiness/sig-instrumentation/4827.yaml

[richabanker]

@rayandas It turns out we will add the new changes while keeping the feature in alpha to get feedback from users about the newly introduced structured API before making it default on.

[rayandas]

@richabanker I see, thanks for the update. With all the requirements satisfied, this KEP is now Tracked for PRR freeze.

[rayandas]

/label tracked/yes

[rayandas]

Hello @richabanker 👋, v1.35 Enhancements team here.

Just checking in as we approach enhancements freeze on Thursday 16th October 2025 (AoE) / Friday 17th October 2025, 12:00 UTC.

This enhancement is targeting stage Beta for v1.35 (correct me, if otherwise)

Here's where this enhancement currently stands:

• [x] KEP readme using the latest template has been merged into the k/enhancements repo.
• [x] KEP status is marked as implementable for latest-milestone: v1.35.
• [x] KEP readme has up-to-date graduation criteria.
• [ ] KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

For this KEP, we would just need to update the following:

• Please get lgtm and approve label on the PR https://github.com/kubernetes/enhancements/pull/5611

The status of this enhancement is marked as At risk for enhancements freeze. Please keep the issue description up-to-date with appropriate stages as well.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[richabanker]

@rayandas https://github.com/kubernetes/enhancements/pull/5611 along with https://github.com/kubernetes/enhancements/pull/5560 is now merged