cri: fix container status#5117
Conversation
|
Hi @Iceber. 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/test-infra repository. |
|
Build succeeded.
|
244fa35 to
75054a0
Compare
|
Build succeeded.
|
75054a0 to
41ba733
Compare
|
Build succeeded.
|
41ba733 to
17dbca9
Compare
|
Build succeeded.
|
Signed-off-by: Iceber Gu <[email protected]>
17dbca9 to
92ab1a6
Compare
|
Build succeeded.
|
|
/ok-to-test |
fix crictl: kubernetes-sigs/cri-tools#724
fix dockershim: kubernetes/kubernetes#99585
In some container states, the startedAt and finishedAt should not be specified
containerd/vendor/k8s.io/cri-api/pkg/apis/runtime/v1alpha2/api.pb.go
Lines 4211 to 4223 in 134f7a7