-
Notifications
You must be signed in to change notification settings - Fork 13
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
Fix CONTAINER_ID with PodSandboxID #213
Conversation
1fc8523
to
1baa88b
Compare
@LionelJouin could you please keep the vendoring changes in an isolated commit ? the github UI doesn't handle well all the changes in this PR (and I'd say 98% of it is on the vendor folder)... That'd help me :) |
Done |
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.
couple of questions; a bit concerned about the kubelet go mod change.
Also, shouldn't we remove the criType
attributes from the CRIO manifest ?
multus-dynamic-networks-controller/manifests/crio-dynamic-networks-controller.yaml
Line 64 in 808c485
"criType": "crio", |
Fixes k8snetworkplumbingwg#209 ADD and DEL were called with the ID of the first container found in the pod spec while the PodSandboxID was required. Refactoring has been done to remove the CRI-O and Containerd communication. Instead, only the CRI API is used.
Use of Pod UID instead of Name/Namespace to get the podSandBoxId and NetNs with the CRI API. Using Pod/Namespace might not be unique if a pod is deleted/created, UID will be unique.
I removed crio from the yaml file in the second commit |
What this PR does / why we need it:
ADD and DEL were called with the ID of the first container found in the pod spec while the PodSandboxID was required.
Refactoring has been done to remove the CRI-O and Containerd communication. Instead, only the CRI API is used.
Which issue(s) this PR fixes:
Fixes #209
Special notes for your reviewer (optional):
E2e for CRI-O and Containerd are still needed, and e2e with a CNI that uses CONTAINER_ID might also be needed.