I have noticed that while upgrading, all containers still seems to be part of the load balancer targets.
e.g. if I spam http get requests to my load balanced service, some times there will be a huge latency when the load balancer hits a container that is currently upgrading.
even if I have a a big batch interval for the upgrade. when a specific instance is upgraded and hit by the balancer, there will be some latency.
Wouldn’t it be possible to have Rancher notifying the loadbalancer before it upgrades a container?
e.g. if you have 3 instances of the container, if instance #1 is about to be upgraded, the load balancer could first remove it from its target list. thus eliminating any quirky latency or bad requests. and add it back to the target list once the container is healthy again.
I might have misinterpreted some of the behavior, but it sure looks like what I observed above is how things work.
even if you add health checks to a service, those checks will not be fine grained enough to ensure complete responsiveness.
Is this the current state or am I misunderstanding something?