-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
Kubelet: implement support for podAndContainerStatsFromCRI #103095
Kubelet: implement support for podAndContainerStatsFromCRI #103095
Conversation
/sig node |
@@ -1272,6 +1385,15 @@ message FilesystemUsage { | |||
// This may not equal InodesCapacity - InodesAvailable because the underlying | |||
// filesystem may also be used for purposes other than storing images. | |||
UInt64Value inodes_used = 4; | |||
// TODO: Unclear how the remaining fields relate to container stats. Is it filled in cAdvisor? |
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.
also TODO: I have yet to actually figure out how to wire these up yet. it's not clear this should be the responsibility of CRI impl or cAdvisor
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.
Does this make more sense as a cumulative stat rather than associating with an ImageSpec for a container?
cb4ee8f
to
e9eecec
Compare
/triage accepted |
fdc3fd5
to
d6b6860
Compare
This looks ready. /lgtm |
} | ||
// CRI implementation doesn't support ListPodSandboxStats, warn and fallback. | ||
klog.V(5).ErrorS(err, | ||
"CRI implementation must be updated to support ListPodSandboxStats if PodAndContainerStatsFromCRI feature gate is enabled. Falling back to populating with cAdvisor; this call will fail in the future.", |
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.
+1 on adding this as a fallback
LGTM as well, thanks @haircommander for your work on this. We plan to add new E2E tests that will validate CRI stats using running against updated container runtime implementations that support the new endpoints. /lgtm |
thanks @haircommander and @bobbypage for the mutual work on this. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bobbypage, derekwaynecarr, haircommander, mikebrow The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
Part of kubernetes/enhancements#2371 Follow up to the initial work introducing CRI API fields for Windows metrics collection kubernetes#110754 Windows equivalent work for adding support for Windows podAndContainerStatsFromCRI kubernetes#103095, which will allow users to get Windows pod and container stats only from CRI. Signed-off-by: mansikulkarni96 <mankulka@redhat.com>
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR uses the CRI changes in #102789 to implement the feature gate for kubernetes/enhancements#2364
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: