Skip to content

adds a list of available HTTP endpoints for the kube-controller-manag… #133218

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

adds a list of available HTTP endpoints for the kube-controller-manag… #133218

wants to merge 1 commit into from
+8 −1

Conversation

nmn3m
Copy link

@nmn3m nmn3m commented Jul 25, 2025

What type of PR is this?

/kind cleanup
/kind documentation

What this PR does / why we need it:

This PR enhances the /statusz page of the kube-controller-manager by including a list of all registered HTTP endpoints exposed by the component.
This provides better visibility into available health, metrics, and debug endpoints, which is particularly valuable for observability and operational tooling.
It aligns with the ongoing effort to improve introspection across Kubernetes control plane components.

Which issue(s) this PR is related to:

Fixes #133182
Part of umbrella issue: #132474

Special notes for your reviewer:

  • This mirrors similar efforts recently merged for kube-scheduler and kube-apiserver.
  • The endpoint list is sorted and clearly grouped to improve readability.
  • Only non-private handlers are shown to avoid leaking sensitive internals.

Does this PR introduce a user-facing change?

The `/statusz` page in `kube-controller-manager` now includes a list of registered HTTP endpoints. This improves debuggability and operational insight into active component routes.

@k8s-ci-robot
Copy link
Contributor

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions 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.

@k8s-ci-robot k8s-ci-robot added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. kind/documentation Categorizes issue or PR as related to documentation. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 25, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions 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.

@k8s-ci-robot
Copy link
Contributor

Hi @nmn3m. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions 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.

@k8s-ci-robot k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jul 25, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: nmn3m
Once this PR has been reviewed and has the lgtm label, please assign soltysh for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@nmn3m
Copy link
Author

nmn3m commented Jul 25, 2025

cc @richabanker

@helayoty
Copy link
Member

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jul 25, 2025
@ylink-lfs
Copy link
Contributor

/ok-to-test

Just a note that PR kube-controller-manager: list available endpoints in /statusz #133200 was opened earlier than this one. Assuming their content is not significantly different, we should handle them on a first-come, first-served basis.

@nmn3m
Copy link
Author

nmn3m commented Jul 27, 2025

/ok-to-test

Just a note that PR kube-controller-manager: list available endpoints in /statusz #133200 was opened earlier than this one. Assuming their content is not significantly different, we should handle them on a first-come, first-served basis.

@ylink-lfs if you took a look at the issue, you will find that @richabanker sent it to me first, as this issue was discussed in the weekly meeting. I was working on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@sjenning sjenning Awaiting requested review from sjenning

@smarterclayton smarterclayton Awaiting requested review from smarterclayton

Assignees
No one assigned
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/documentation Categorizes issue or PR as related to documentation. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

List available endpoints for kube-controller-manager's /statusz
4 participants
@nmn3m @k8s-ci-robot @helayoty @ylink-lfs