Hi ,
we are facing the issue with un-even load balancing done by kong when upstream host is kubernetes Cluster IP based service .
Kong maintain the connection to old pods tied to Cluster IP even when the upstream new pods are arrived after deployment linked with the upstream service .
we seen the issue that kong doesnot close the connection by itself , it relies on up-stream to close the connection , any way in kong 1.2.2 where we can configure kong to close the connection in the configured time interval .