OpenShift service with sessionAffinity forwards traffic to two pods OpenShift service with sessionAffinity forwards traffic to two pods kubernetes kubernetes

OpenShift service with sessionAffinity forwards traffic to two pods


Looking at the Kubernetes proxysocket source, we assume that a long connection time (above 250 ms) triggers the selection of a new endpoint.

Instead of distributing client connections between the servers via an OpenShift service, we now use an additional nginx pod between client and servers.