Rancher load balancer hangs in networking state

Hi, During a deployment to rancher I have found the rancher load balancers come up variably. Sometimes they come up before the app containers, and sit in a wait state which could be expected. However, sometimes one might hang in a “networking” state. I presume this means network is overloaded, and it is still fulling changes to its host? We do use the --force-upgrade flag during our deployments.

I’m wondering if there is something I am overlooking? Unfortunately, I do not have an image of network I/O for this host at this time, but I imagine it is something that others may have experienced?

Our cloud provider is AWS, and the instance type sizes are m4.xlarge at 750 Mbps dedicated bandwidth.

Thanks -