Fix CNI issue where CNI DEL is never executed#12923
Conversation
295c5e6 to
414e9c0
Compare
414e9c0 to
17da2b1
Compare
Signed-off-by: Michael Zappa <[email protected]>
d355072 to
39e81c3
Compare
Signed-off-by: Michael Zappa <[email protected]>
39e81c3 to
1092b85
Compare
Signed-off-by: Michael Zappa <[email protected]>
af9aec3 to
96dee5f
Compare
|
/cherry-pick release/2.2 |
|
@MikeZappa87: only containerd org members may request cherry picks. If you are already part of the org, make sure to change your membership to public. Otherwise you can still do the cherry-pick manually. 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. |
|
/cherry-pick release/1.7 |
|
@MikeZappa87: #12923 failed to apply on top of branch "release/1.7": 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. |
|
/cherry-pick release/2.2 |
|
/cherry-pick release/2.1 |
|
@MikeZappa87: new pull request created: #12926 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. |
|
@MikeZappa87: new pull request created: #12927 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. |
|
/cherry-pick release/2.0 |
|
@chrishenzie: new pull request created: #13178 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. |
|
Did I forget 2.0! Ha thanks @chrishenzie for getting this, you might need to do some manual changes. |
|
@MikeZappa87 No worries, we're just tackling this as part of reviving the 2.0 branch to extend support. I'm putting together a manual cherry-pick that includes the lint fixes |
We have seen a condition, where the CNI ADD is executed, and containerd exits before the cniResult is saved to disk. When containerd recoverys the StopPodSandbox is called, but skips the CNI DEL because the CNI result is nil. The idea here is to ignore errors from the CNI DEL and try to do a best effort cleanup. The alternative is that a leaked resource could still exist which has been observed.
We see the RunPodSandbox + StopPodSandbox RPC's executed, just no CNI DEL cmd is viewed.