-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Add Windows pod sandbox stats information to KEP 2371 - cri pod container stats #3439
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
Add Windows pod sandbox stats information to KEP 2371 - cri pod container stats #3439
Conversation
acae793 to
1fa4600
Compare
|
/assign @haircommander @bobbypage @dchen1107 |
|
|
||
| The field `LinuxPodSandboxStats` would stay the same (with duplicated fields) for backwards compatibility. We will also leave `WindowsPodSandboxStats` with a comment that it is not currently used. This option allows us to add specific fields in the future, Linux and Windows sub fields could be added to `LinuxPodSandboxStats` and `WindowsPodSandboxStats` if there are use cases for specific fields. | ||
|
|
||
| The downside to this approach is that we have two fields (`LinuxPodSandboxStats` and `PodSandboxStats`) which are initially identical. We could mark the individual fields in the `LinuxPodSandboxStats` as depreciated and allow only new linux only fields be added to `LinuxPodSandboxStats`. |
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.
I think this approach makes sense. I think we should mention that eventually we will drop LinuxPodSandboxStats and WindowsPodSandboxStats in favor of the single structure
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.
sounds good, I was thinking that we could possibly use the fields in the future for OS specific stats but probably better to handle at a later point if it ever comes up 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.
updated
|
one more set of notes, but the approach LGTM |
1fa4600 to
c896c46
Compare
IIRC when this was discussed on the July 19th meeting we decided there wasn't a known use-case for having separate structs. Someone (I think @dchen1107 and/or @bobbypage ) stated that these metrics were primary used by the kubelet for eviction and metrics-server for scaling purposed. |
That was my understanding as well. At sig-node meeting today, there was an update on the performance for moving the additional cadvisor metrics into the ListStats API: https://docs.google.com/document/d/1Ne57gvidMEWXR70OxxnRkYquAoMpt56o75oZtg-OeBg/edit#heading=h.i2n5jj2i4vso In the proposal Linux specific fields are added to the stats call. I wasn't aware of this use case, but if this is the direction, then I think we would want to have these fields as separate as was initially proposed. |
|
@bobbypage @haircommander @mikebrow I have this on the agenda to discuss tomorrow. I won't be able to make it but @marosset is going to attend. Hopefully we can get some consensus on the direction forward. Thanks! |
Signed-off-by: James Sturtevant <[email protected]>
2845607 to
73a5c8d
Compare
|
After further discussion at sig-node on Sep 13th, it was decided that we will keep Windows and Linux fields separate. I've updated the KEP @haircommander @marosset @bobbypage @dcantah |
|
/milestone v1.26 |
| - balancing_enabled | ||
| - dm_operation_in_progress | ||
|
|
||
| These are not used currently but are be very specific to each implementation and could be collected by specialized tools on a as needed basis. |
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.
or maybe reported as an unstructured Metric through the endpoint formally known as /metrics/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.
had the same thoughts, exposing them through that would be a good way to provide them to end users. If kubelet ends up needing them for decisions, we could introduce them to the formal Pod Stats call but can be done at a later time if need arises
|
/lgtm there's one leading question I added, but I don't think we need to hammer out the details of it yet. edit: oops, missed #3439 (comment), I'm on standby to re-lgtm :) |
Co-authored-by: Danny Canter <[email protected]>
|
/lgtm |
|
After further discussion at sig-node on Sep 13th, it was decided that we will keep Windows and Linux fields separate. The KEP has been updated to reflect this. /assign @dchen1107 @mrunalp @mikebrow |
|
/lgtm |
|
/assign @derekwaynecarr |
|
/lgtm |
|
/cc @mikebrow @derekwaynecarr for 1.26 enhancement freeze |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: derekwaynecarr, jsturtevant The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: James Sturtevant [email protected]
Adding Windows stats details to the cri pod container stats KEP
After opening kubernetes/kubernetes#110754 we discovered there was more design work need for Windows and was suggested at sig-node to do the work in KEP.
/sig windows
/sig node