You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whichever cni gets put second, it fails setting up cni, and pod does not get started. I'm not aware of any other way to get communication working between pods on the aws-cni, and pods on the calico-cni. Traffic works fine from calico-cni to aws-cni.
ERRORS
Warning FailedCreatePodSandBox 21s kubelet, ip-100-98-195-17.ec2.internal Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "336230b32313a625e8e6e0245de34f86f84e5dbc80e3eee4a8aecd110bb3c0fa" network for pod "prometheus-prometheus-0": networkPlugin cni failed to set up pod "prometheus-prometheus-0_prom" network: CNI Genie Add IP internal error: Error from cni: add command: failed to setup network: setupNS network: failed to setup NS network: setup NS network: failed to add default route: file exists, result: %!!(MISSING)s(<nil>)
The text was updated successfully, but these errors were encountered:
K8s version: EKS 1.17.7
cni-genie: release 1.8
Pod Annotations: cni: calico,aws
Whichever cni gets put second, it fails setting up cni, and pod does not get started. I'm not aware of any other way to get communication working between pods on the aws-cni, and pods on the calico-cni. Traffic works fine from calico-cni to aws-cni.
ERRORS
The text was updated successfully, but these errors were encountered: