-
Notifications
You must be signed in to change notification settings - Fork 6.7k
crio: add option pull_progress_timeout #12555
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
base: master
Are you sure you want to change the base?
crio: add option pull_progress_timeout #12555
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: pedro-peter The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @pedro-peter. Thanks for your PR. I'm waiting for a kubernetes-sigs 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-sigs/prow repository. |
# ignore; the latter will ignore volumes entirely. | ||
image_volumes = "mkdir" | ||
|
||
{% if crio_pull_progress_timeout is defined %} |
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.
Could crio_pull_progress_timeout
set the default value instead of is defined
?
crio_selinux: "{{ (preinstall_selinux_state == 'enforcing') | lower }}" | ||
crio_signature_policy: "{% if ansible_os_family == 'ClearLinux' %}/usr/share/defaults/crio/policy.json{% endif %}" | ||
# Override the default pull progress timeout | ||
#crio_pull_progress_timeout: "60s" |
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.
Align with CRI-O default.
What type of PR is this?
What this PR does / why we need it:
pulling large container images can fail with error:
releated crio issues:
cri-o/cri-o#8760
cri-o/cri-o#8764
A PR was opened in crio 1.32 & backported to crio 1.30, 1.31:
cri-o/cri-o#8765
to add option
pull_progress_timeout
This PR adds the option to the crio.conf so it can be set if needed (and leave it disabled by default)
Which issue(s) this PR fixes:
Fixes #12554
Special notes for your reviewer:
Does this PR introduce a user-facing change?: