Amazon-vpc-cni-k8s: aws-cni chaining with linkerd-cni from linkerd2

[caleygoff-invitae]

I am curious if the aws-cni plugin allows for chaining with the linkerd2 linkerd-cni. I see a few issues open where this was allowed for the bandwidth plugin, and there is there is documentation out there with cilium and calico. Essentially I have been advised that if we can control the startup order of the cnis, where the aws-cni starts first and then the linkerd-cni ds starts afterwards, the linkerd service mesh will work with the network capabilities that aws-cni provides.

I am not sure how to go about this with aws-cni, any thoughts or feedback will be appreciated

Environment:

• Kubernetes version (use kubectl version):1.17
• CNI Version: 1.6.1
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):

[jayanthvn]

Hi @caleygoff-invitae

We are currently blocked on supporting chaining for bandwidth plugin because of this - https://github.com/containerd/cri/issues/1544. I can explore if we have similar issues chaining with linkerd-cni and get back to you soon.

Thanks.

[caleygoff-invitae]

Many thanks @jayanthvn !!

[kivagant-ba]

@jayanthvn, have you had a chance to test amazon-vpc-cni coupling with linkerd-cni? Any chance it would work?

[jayanthvn]

Hi @kivagant-ba

Sorry haven't got a chance to check. I need to follow up on this - containerd/cri#1544. Since with chaining we had seen issue with containerd. Will look into it and update as soon as possible.