-
Notifications
You must be signed in to change notification settings - Fork 41.1k
feat: list available endpoints in /statusz for kubelet #133199
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.
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
base: master
Are you sure you want to change the base?
feat: list available endpoints in /statusz for kubelet #133199
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ylink-lfs 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 |
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR restores the display of useful endpoint links in the kubelet's /statusz
page. The change adds a list of important kubelet endpoints (/livez, /readyz, /healthz, /metrics) to the statusz registry, making them visible on the status page for easier debugging and introspection.
- Adds endpoint listing functionality to the kubelet's
/statusz
handler - Includes four key endpoints: health checks and metrics
Hi @ylink-lfs. 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 Once the patch is verified, the new status will be reflected by the 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. |
/ok-to-test |
3f1f77c
to
660bd61
Compare
pkg/kubelet/server/server.go
Outdated
statusz.Install(s.restfulCont, ComponentKubelet, statusz.NewRegistry( | ||
compatibility.DefaultBuildEffectiveVersion(), | ||
statusz.WithListedPaths([]string{ | ||
"/livez", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This paths are actually path strings from actual handlers, which could be changed separately and bring inconsistency. Wouldn't it be better to introduce constant variables with string or something like that, so that path strings are changed in single place?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated the path declaration, PTAL
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we dont want to hardcode the paths here, since the paths exposed can change with every release. We should do something similar to what we are doing for apiserver here i.e. make use of the handler's ListedPaths()
to get the true list of exposed paths.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we dont want to hardcode the paths here, since the paths exposed can change with every release. We should do something similar to what we are doing for apiserver here i.e. make use of the handler's
ListedPaths()
to get the true list of exposed paths.
I implemented a commit based on the example you provided. PTAL if my idea is correct?
3107695
to
4b3481f
Compare
7a6c1b5
to
652972f
Compare
652972f
to
416a7e7
Compare
@ylink-lfs: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Previously api-machinery members removed the hard-coded paths (/healthz, /livez, /readyz) in staging package. Should restore the 'Useful links' used by kubelet.
Which issue(s) this PR is related to:
Umbrella issue: #132474
Fixes: #133184
Special notes for your reviewer:
Tested locally with a custom build of kube-proxy confirming that /statusz correctly shows the listed endpoints.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: