1<!-- Thanks for sending a pull request!
2
3Please be aware that we're following the Kubernetes guidelines of contributing
4to this project. This means that we have to use this mandatory template for all
5of our pull requests.
6
7Please also make sure you've read and understood our contributing guidelines
8(https://github.com/cri-o/cri-o/blob/master/CONTRIBUTING.md) as well as ensuring
9that all your commits are signed with `git commit -s`.
10
11Here are some additional tips for you:
12
13- If this is your first time, please read our contributor guidelines:
14 https://git.k8s.io/community/contributors/guide#your-first-contribution and
15 developer guide
16 https://git.k8s.io/community/contributors/devel/development.md#development-guide
17- Please label this pull request according to what type of issue you are
18 addressing, especially if this is a release targeted pull request. For
19 reference on required PR/issue labels, read here:
20 https://git.k8s.io/community/contributors/devel/sig-release/release.md#issuepr-kind-label
21- If you want *faster* PR reviews, read how:
22 https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
23- If the PR is unfinished, see how to mark it:
24 https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests
25-->
26
27#### What type of PR is this?
28
29<!--
30Uncomment only one `/kind <>` line, hit enter to put that in a new line, and
31remove leading whitespace from that line:
32-->
33
34<!--
35/kind bug
36/kind cleanup
37/kind documentation
38/kind feature
39
40Optionally add one or more of the following kinds if applicable:
41/kind api-change
42/kind deprecation
43/kind failing-test
44/kind flake
45/kind regression
46-->
47
48#### What this PR does / why we need it:
49
50#### Which issue(s) this PR fixes:
51
52<!--
53Automatically closes linked issue when PR is merged.
54Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
55-->
56
57<!--
58Fixes #
59or
60None
61-->
62
63#### Special notes for your reviewer:
64
65#### Does this PR introduce a user-facing change?
66
67<!--
68If no, just write `None` in the release-note block below. If yes, a release note
69is required: Enter your extended release note in the block below. If the PR
70requires additional action from users switching to the new release, include the
71string "action required".
72
73For more information on release notes see:
74https://git.k8s.io/community/contributors/guide/release-notes.md
75-->
76
77```release-note
78
79```
View as plain text