statusz: move componentName into registry#135091
statusz: move componentName into registry#135091richabanker wants to merge 1 commit intokubernetes:masterfrom
Conversation
b53bbe6 to
9c3802a
Compare
|
LGTM label has been added. DetailsGit tree hash: 8c0d67f28403780605d44f024ca699763dfbce9a |
|
/remove-sig api-machinery |
|
/triage accepted |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dgrisonnet, richabanker The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Moves componentName into statusz registry. Previously, componentName was passed separately to statusz handler's Install(). This establishes a cleaner pattern where the registry is the single source of truth for all statusz metadata
Which issue(s) this PR is related to:
kubernetes/enhancements#4827
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: