Flagz for Kubernetes Components

[richabanker]

Enhancement Description

• Introduces a flagz page for all core components.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-instrumentation/4828-component-flagz/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):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): KEP for flagz page for Kubernetes Components #4831
  • Code (k/k) update PR(s):
    • add OWNERS and README for zpages under component-base kubernetes#127206
    • Add flagz endpoint for apiserver kubernetes#127581
    • test: Add integration test for apiserver flagz endpoint kubernetes#128848
    • feat: Add flagz endpoint for kubelet kubernetes#128857
    • feat: Add flagz endpoint for kube-scheduler kubernetes#128818
    • feat: Add flagz endpoint for kube-controller-manager kubernetes#128824
    • feat: Add flagz endpoint for kube-proxy kubernetes#128985
    • Move zpages common code to an httputil package kubernetes#128925
    • [KEP-4828] Flagz versioned structured response kubernetes#134995
  • Docs (k/website) update PR(s):
    • Add docs for zpages website#48760
    • Add blog for zpages website#48369

[richabanker]

/assign

[richabanker]

/sig instrumentation

[dipesh-rawat]

Hello @richabanker 👋, v1.32 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)

/stage alpha

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 3rd October 2024 so that the PRR team has enough time to review your KEP.

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

• Create the KEP readme using the latest template and merge it in the k/enhancements repo.
• Ensure that the KEP has undergone a production readiness review and has been 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. Thank you!

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

[mattbailey]

Hello, I'd like to shadow PRR review here, thanks!