Use containerd.sock for AmazonVPC CNI with containerd #10502
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k8s-ci-robot
added
the
cncf-cla: yes
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman 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 |
|
/cc @rifelpet @MoShitrit |
k8s-ci-robot
added
size/XS
hakman
force-pushed
the
amazonvpc-cni-containerd
branch
3 times, most recently
from
72e7ec6
to
2e05eee
Compare
k8s-ci-robot
added
size/XL
hakman
force-pushed
the
amazonvpc-cni-containerd
branch
from
2e05eee
to
41d7490
Compare
|
/lgtm |
k8s-ci-robot
added
the
lgtm
k8s-ci-robot
added a commit
that referenced
this pull request
Dec 28, 2020
…-upstream-release-1.19 Automated cherry pick of #10502: Use containerd.sock for AmazonVPC CNI with containerd
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Amazon VPC CNI requires access to the CRI socket to get the local container info:
xRef: aws/amazon-vpc-cni-k8s#371
This is the reason the periodic test for Amazon VPC CNI is failing since switching it to containerd:
https://testgrid.k8s.io/kops-network-plugins#kops-aws-cni-amazon-vpc
There are proposed changes to get away from the "dockershim" name, but still not merged:
xRef: aws/amazon-vpc-cni-k8s#1175