Update crictl.yaml to reflect cri-tools v1.19.0 configs #4162
Conversation
The new configuration values in cri-tools v1.19.0 should be added to our vendored config as well. Signed-off-by: Sascha Grunert <[email protected]>
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov Report
@@ Coverage Diff @@
## master #4162 +/- ##
=======================================
Coverage 40.76% 40.76%
=======================================
Files 111 111
Lines 9494 9494
=======================================
Hits 3870 3870
Misses 5248 5248
Partials 376 376 |
|
LGTM |
|
/retest |
|
@saschagrunert: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
|
/retest |
|
/cherry-pick release-1.19 |
|
@saschagrunert: new pull request created: #4185 DetailsIn 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. |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
The new configuration values in cri-tools v1.19.0 should be added to our vendored config as well.
Which issue(s) this PR fixes:
Follow-up of #4150
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?