This message was deleted.
# general
a
This message was deleted.
q
How is your control layer sized (number of CP nodes and etcd nodes, vm sizes, storage type, ...). Is etcd performing ok? Have you seen errors/warnings/timeout on the etcd's log?
I can't really help with the AWS CNI driver but we can have a look at possible bottlenecks.
Have you already opened a support ticket?
l
CP Nodes are c5n.4xlarge. ECTD Are m5.2xlarge. The ETCD nodes have GP2 volumes of 750Gig ( 2250 IOPS ) This was on Rancher 2.5.8. We are now trying the same setup on 2.6.7.
q
Can you keep an eye on the alarms and the performance-related issues mentioned here: https://docs.ranchermanager.rancher.io/troubleshooting/kubernetes-components/troubleshooting-etcd-nodes. I always try to discard any possible issue on the etcd side when doing this type of trouble shooting. It's also very important to look for "apply entries took too long" messages in the log as it's a clear hint that etcd is having issues. (https://etcd.io/docs/v3.1/faq/#what-does-the-etcd-warning-apply-entries-took-too-long-mean)