-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[cri] Implement CRI Pod and Container stats for Windows #7099
Conversation
Hi @jsturtevant. Thanks for your PR. I'm waiting for a containerd 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/test-infra repository. |
@jsturtevant: GitHub didn't allow me to request PR reviews from the following users: haircommander, marosset, bobbypage. Note that only containerd members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this: 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/test-infra repository. |
6b33d83
to
77b7464
Compare
The linter is failing on mac because I pulled two functions up that would allow me to re-use code across the windows and linux implementations.
They are not used in the |
Moved We discussed CRI changed required at sig-node this morning and we will be do a bit more design via the KEP. Once those are merged, I can refresh this PR but wouldn't anticipate drastic changes to the design except may what values we return. |
We've reach consensus on the changes to CRI: kubernetes/enhancements#3439 and the cri changes have been updated in kubernetes/kubernetes#110754 |
77b7464
to
8527033
Compare
with the cri api update in #7656 this work can continue 🚀. I've rebased and fixed it up to use the new fields. Next step is to clean it up and get it ready for review. |
a682290
to
618ebd7
Compare
806ae42
to
6b45e96
Compare
Should this issue get added to the 1.7 milestone? |
@dmcgowan thoughts? |
@containerd/maintainers this is ready for final review |
ed90205
to
830a9c5
Compare
830a9c5
to
39b6a5d
Compare
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.
LGTM. Thanks!
Lgtm |
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.
LGTM
@jsturtevant Can you squash this? I think we're good for check-in after. |
Signed-off-by: James Sturtevant <jstur@microsoft.com>
Signed-off-by: James Sturtevant <jstur@microsoft.com>
39b6a5d
to
32ed559
Compare
I left the changes separate from Cri Sandbox code and sandbox. Let me know if I should squash to a single commit |
@jsturtevant That's fine, makes it easier to revert if anything was wrong in one and not the other |
Implements
ListPodSandboxStats
andPodSandboxStats
for Windows.Part of kubernetes/enhancements#2371
Currently is using the branch from kubernetes/kubernetes#110754 for the CRI API updates that were needed for Windows
Special notes for your reviewer:
Still need to add some tests and refactor some of the linux functionality to be able to implement
UsageNanoCores
.I made a custom build of crictl that can handle the windows stats but can use any version that has the
statsp
command.