Statusz for Kubernetes Components

[richabanker]

Enhancement Description

• Introduces a statusz page for all core components.
• Kubernetes Enhancement Proposal: KEP for statusz page for Kubernetes Components #4830
• 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
  • KEP (k/enhancements) update PR(s): KEP for statusz page for Kubernetes Components #4830
  • Code (k/k) update PR(s):
  • 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).