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
The first pods scheduled on a node can sometimes get an IP from the non-default CNI.
I think this is because CNI-Genie daemonset pod can start too late maybe due to delays in pulling the image.
I added the system-node-critical priorityClass to the CNI-Genie daemonset but it has not helped.
Example timeline:
Nginx app pod triggers cluster scale up
AWS-CNI, Calico and CNI-Genie daemonsets are scheduled on the new node
Nginx pod starts up before GNI-Genie pod has finished starting so the config is not in /etc/cni/net.d at this point
Nginx pod gets an IP from AWS-CNI instead of the default set in CNI-Genie
Future pods on that new node are given correct IPs once CNI-Genie has started
Hi,
The first pods scheduled on a node can sometimes get an IP from the non-default CNI.
I think this is because CNI-Genie daemonset pod can start too late maybe due to delays in pulling the image.
I added the system-node-critical priorityClass to the CNI-Genie daemonset but it has not helped.
Example timeline:
Setup:
Cluster: Amazon EKS 1.18
Calico version: 3.16.3
CNI-Genie version: latest
The text was updated successfully, but these errors were encountered: