-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Add support for CRI verbose
fields
#107945
Conversation
/test pull-kubernetes-node-e2e-containerd |
febd84f
to
9c84e27
Compare
9c84e27
to
554825a
Compare
/test pull-kubernetes-node-e2e-containerd |
/retest |
/test pull-kubernetes-node-e2e-containerd |
55427a3
to
6a33e8f
Compare
/assign (important soon as needed for cri tools) |
/cc haircommander @mrunalp |
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.
LGTM except for the nit.
The remote runtime implementation now supports the `verbose` fields, which are required for consumers like cri-tools to enable multi CRI version support. Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
6a33e8f
to
10b9407
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.
/lgtm
/milestone v1.24 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mrunalp, pacoxu, 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 |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
The remote runtime implementation now supports the
verbose
fields,which are required for consumers like cri-tools to enable multi CRI
version support.
Which issue(s) this PR fixes:
Refers to kubernetes-sigs/cri-tools#889
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: