-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add dynamic image pull timeout #7887
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
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saschagrunert 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 |
45857bd to
7e1adef
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #7887 +/- ##
==========================================
- Coverage 48.87% 48.86% -0.01%
==========================================
Files 152 152
Lines 16447 16456 +9
==========================================
+ Hits 8038 8042 +4
- Misses 7433 7437 +4
- Partials 976 977 +1 |
|
/retest |
7e1adef to
afec6c3
Compare
|
/retest |
|
/test ci-e2e |
|
/retest |
We now support a pull context which can actually be cancelled. This way we can combine the pull progress together with a dynamic timeout, which cancels the context if no progress is being made on pull. Signed-off-by: Sascha Grunert <[email protected]>
afec6c3 to
1a377cc
Compare
|
/retest |
|
/test e2e-gcp-ovn |
|
@cri-o/cri-o-maintainers PTAL |
|
I think this would fix #6574 as well |
| // It also checks if progress is being made within a constant timeout. | ||
| // If the timeout is reached because no progress updates have been made, then | ||
| // the cancel function will be called. | ||
| func progressGoRoutine(ctx context.Context, cancel context.CancelFunc, progress <-chan imageTypes.ProgressProperties, remoteCandidateName storage.RegistryImageReference) { |
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.
nit: maybe consumeImagePullProgress or something?
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.
Sure, following-up in #7946
|
/lgtm nit can be addressed async, or ignored |
|
/retest |
|
/test e2e-gcp-ovn |
|
/retest-required |
Follow-up on cri-o#7887 (comment) Signed-off-by: Sascha Grunert <[email protected]>
This allows to set a pull timeout (currently not used neither by the kubelet nor cri-tools) using the CRI context. Future consumers can then limit the pul not only if no network traffic is available (introduced in \cri-o#7887), but also in a more general way. Signed-off-by: Sascha Grunert <[email protected]>
Add the option to be able to fine-tune the pull progress timeout or even disable it. Fixes cri-o#8764 and cri-o#8760 Follow-up on: cri-o#7887 Signed-off-by: Sascha Grunert <[email protected]>
Add the option to be able to fine-tune the pull progress timeout or even disable it. Fixes cri-o#8764 and cri-o#8760 Follow-up on: cri-o#7887 Signed-off-by: Sascha Grunert <[email protected]>
Add the option to be able to fine-tune the pull progress timeout or even disable it. Fixes cri-o#8764 and cri-o#8760 Follow-up on: cri-o#7887 Signed-off-by: Sascha Grunert <[email protected]>
Add the option to be able to fine-tune the pull progress timeout or even disable it. Fixes cri-o#8764 and cri-o#8760 Follow-up on: cri-o#7887 Signed-off-by: Sascha Grunert <[email protected]>
Add the option to be able to fine-tune the pull progress timeout or even disable it. Fixes cri-o#8764 and cri-o#8760 Follow-up on: cri-o#7887 Signed-off-by: Sascha Grunert <[email protected]>
Add the option to be able to fine-tune the pull progress timeout or even disable it. Fixes cri-o#8764 and cri-o#8760 Follow-up on: cri-o#7887 Signed-off-by: Sascha Grunert <[email protected]>
Add the option to be able to fine-tune the pull progress timeout or even disable it. Fixes cri-o#8764 and cri-o#8760 Follow-up on: cri-o#7887 Signed-off-by: Sascha Grunert <[email protected]>
Add the option to be able to fine-tune the pull progress timeout or even disable it. Fixes cri-o#8764 and cri-o#8760 Follow-up on: cri-o#7887 Signed-off-by: Sascha Grunert <[email protected]>
Add the option to be able to fine-tune the pull progress timeout or even disable it. Fixes cri-o#8764 and cri-o#8760 Follow-up on: cri-o#7887 Signed-off-by: Sascha Grunert <[email protected]>
Add the option to be able to fine-tune the pull progress timeout or even disable it. Fixes cri-o#8764 and cri-o#8760 Follow-up on: cri-o#7887 Signed-off-by: Sascha Grunert <[email protected]>
Add the option to be able to fine-tune the pull progress timeout or even disable it. Fixes cri-o#8764 and cri-o#8760 Follow-up on: cri-o#7887 Signed-off-by: Sascha Grunert <[email protected]>
Add the option to be able to fine-tune the pull progress timeout or even disable it. Fixes cri-o#8764 and cri-o#8760 Follow-up on: cri-o#7887 Signed-off-by: Sascha Grunert <[email protected]>
What type of PR is this?
/kind feature
What this PR does / why we need it:
We now support a pull context which can actually be cancelled. This way we can combine the pull progress together with a dynamic timeout, which cancels the context if no progress is being made on pull.
Which issue(s) this PR fixes:
Refers to #7885
Special notes for your reviewer:
cc @mrunalp
Does this PR introduce a user-facing change?