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
plugins/cilium-cni: fix aws-cni cni chaining #15915
Conversation
AWS-CNI seems to require more fields than the ones hard coded in Cilium image. This patch adds the missing fields. Error messages that might show up in pod describe are similar as: ``` network: invalid character '{' after top-level value ``` or ``` \n{\n \"code\": 100,\n \"msg\": \"add cmd: failed to assign an IP address to container\"\n}": invalid character '{' after top-level value ``` Signed-off-by: André Martins <andre@cilium.io>
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.
This matches the reported fixes in aws/amazon-vpc-cni-k8s#1314 .
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.
LGTM, can you provide more context like linking what changed in the aws-cni in the commit msg itself?
test-me-please |
@christarazi I had a quick look and couldn't easily find anything, it'd be helpful to know which version worked and which one broke. |
test-1.16-netnext (previous https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-net-next/409/) |
hitting #15998 |
AWS-CNI seems to require more fields than the ones hard coded in Cilium
image. This patch adds the missing fields.
Error messages that might show up in pod describe are similar as:
or
Signed-off-by: André Martins andre@cilium.io