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.35
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): KEP for statusz page for Kubernetes Components #4830
  • Code (k/k) update PR(s):
    • add OWNERS and README for zpages under component-base kubernetes#127206
    • Move k8s.io/apiserver/pkg/util/version to component-base kubernetes#128196
    • Add statusz endpoint for apiserver kubernetes#125577
    • test: Add integration test for apiserver statusz endpoint kubernetes#129366
    • add statusz endpoint for kubelet kubernetes#128811
    • Add statusz endpoint for kube-controller-manager kubernetes#128991
    • Add statusz endpoint for kube-proxy kubernetes#128989
    • Add statusz endpoint for kube-scheduler kubernetes#128987
    • Move zpages common code to an httputil package kubernetes#128925
  • Docs (k/website) update PR(s):
    • Add docs for zpages website#48760
    • Add blog for zpages website#48369
• Beta
  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
  • Docs (k/website) update(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:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.32.
• 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!