-
Notifications
You must be signed in to change notification settings - Fork 40k
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 disk api cri update #120914
Kubelet disk api cri update #120914
Conversation
87cb191
to
da186e3
Compare
/sig node |
/retest |
da186e3
to
a2fa628
Compare
/retest |
1 similar comment
/retest |
/triage accepted |
a2fa628
to
dc44935
Compare
// ImageFsInfo returns information of the filesystem that is used to store images. | ||
func (r *remoteImageService) ImageFsInfoV2(ctx context.Context) (*runtimeapi.ImageFsInfoResponse, error) { | ||
// Do not set timeout, because `ImageFsInfo` takes time. | ||
// TODO(random-liu): Should we assume runtime should cache the result, and set timeout here? |
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 copied these TODO from the previous one but I don't really know if these will ever be valid. Left them in for now.
d01341a
to
229387e
Compare
/retest |
bd2dbad
to
c1a1f85
Compare
/cc @ffromani |
c1a1f85
to
c078bee
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.
couple nits
e8986cf
to
94ff9cf
Compare
Co-authored-by: Mike Brown <brownwm@us.ibm.com>
94ff9cf
to
8ae0d39
Compare
/retest |
/lgtm |
LGTM label has been added. Git tree hash: 26e8c914195f0ab6b4ce6a4696c49977aec1d154
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kannon92, mrunalp 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 |
We should not merge API changes and implementation separately, basically because we can not test it and we can not predice they are not going to be changes during the implementation ... |
What type of PR is this?
/kind feature
What this PR does / why we need it:
As part of Split Image Filesystem KEP, we will update CRI with our KEP design.
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.: