[release/1.6] Ensure the CRIAPIV1Alpha2 warning's lastOccurrence is accurate#10582
Conversation
|
@chrishenzie: GitHub didn't allow me to request PR reviews from the following users: tallclair. Note that only containerd members and repo collaborators can review this PR, and authors cannot review their own PRs. 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-sigs/prow repository. |
|
Hi @chrishenzie. Thanks for your PR. I'm waiting for a containerd 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. 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-sigs/prow repository. |
|
Can you use |
|
/ok-to-test |
This helps gather more accurate API usage data that informs efforts on how to safely migrate containerd clients to 2.0. Signed-off-by: Chris Henzie <[email protected]> (cherry picked from commit 52b79f3) Signed-off-by: Chris Henzie <[email protected]>
chrishenzie
force-pushed
the
v1alpha2-cri-api-warnings-1.6
branch
from
bdc45c9 to
d727961
Compare
Done, thanks! |
samuelkarp
changed the title
4 participants
This helps gather more accurate API usage data that informs efforts on how to safely migrate containerd clients to 2.0.
This is a chery-pick of #10571.
/cc @samuelkarp @tallclair
/hold
Waiting on 1.7 PR to be merged first.