I have small nodejs app running replicated with two pods on cluster with two nodes.

However, it seems that connection is not sticky. I need it to be sticky because I use websocket.

Is sessionAffinity not working with LoadBalancer on GCE? Let me know if i can provide more info. Thanks

Finally I had some time for more experiments:

It seems like the sessionAffinity stops working if the rc is deleted and created again after the service was created.

Steps to reproduce:

• 1) Used following files:

ServerName.yaml

apiVersion: v1
kind: ReplicationController
metadata:
  name: servername
  labels:
    name: servername
spec:
  replicas: 10
  selector:
    name: servername
  template:
    metadata:
      labels:
        name: servername
    spec:
      containers:
      - name: app
        image:  fibheap/printhostname
        imagePullPolicy: "Always"
        ports:
             - containerPort: 80

ServerNameSv.yaml

apiVersion: v1
kind: Service
metadata:
  name: servername
  labels:
    name: servername
spec:
  ports:
    # the port that this service should serve on
    - port: 80
      targetPort: 80
  selector:
    name: servername
  type: LoadBalancer
  sessionAffinity: ClientIP

Dockerfile

FROM google/nodejs

WORKDIR /app

ADD ./main.js /app/main.js

EXPOSE 80
CMD ["node", "--harmony", "./main.js"]

main.js

// Load the http module to create an http server.
var http = require('http');
var os = require('os');

// Configure our HTTP server to respond with Hello World to all requests.
var server = http.createServer(function (req, res) {
  res.writeHead(200, {"Content-Type": "text/plain"});
  var ip = req.headers['x-forwarded-for'] ||
     req.connection.remoteAddress ||
     req.socket.remoteAddress ||
     req.connection.socket.remoteAddress;

  res.end("CIP:" + ip + "  Remote Server:" + os.hostname());
});

// Listen on port 8000, IP defaults to 127.0.0.1
server.listen(80);

// Put a friendly message on the terminal
console.log("Server running at http://127.0.0.1:80/");

• 2) create rc and service (describe service to get IP and assure ClientIP is set)

• 3) curl multiple times from loadbalancer ip -> pod name should stay the same

• 4) delete rc and create again

• 5) curl again multiple time -> pod name changes

Please let me know if that helps for reproducing. Please feel free to use docker repository fibheap/printhostname directly