title: kubernetes session affinity behavior
body: <p>I am using kubernetes 1.9.2 created but kubeadm.
  this kubernetes cluster is running in 4 ec2 nodes.</p>
  
  <p>I have a deployment that requires using cache in every pod.
  in order to accomlish that we used session affinity from ClusterIP.</p>
  
  <p>since I was ELB in front of my Kubernetes cluster I wonder how the session affinity is behaving.</p>
  
  <p>the natural behavior would be that for every client IP a different will get the requests but given the traffic is transferred via ELB , whoch IP does the session affinity recognizes , the ELB IP or the actual Client IP?</p>
  
  <p>when I check the traffic to the pods I see that 102 pods get all the requests and the 2 other pods are just waiting.</p>
  
  <p>many thanks for any help.</p>