Selenium on Kubernetes!

README.md

This is a quick and dirty guide on how to deploy Selenium on Kubernetes.

It is required that you have Kubernetes cluster up and running. If you don't have one, GKE is pretty nifty: https://cloud.google.com/container-engine/

Deploy the Seleniumb Hub:

kubectl create -f selenium-hub-rc.yaml
kubectl create -f selenium-hub-svc.yaml

Deploy some Firefox and Chrome pods:

kubectl create -f selenium-node-chrome-rc.yaml
kubectl create -f selenium-node-firefox-rc.yaml

Grab the Service ip or nodeport:

kubectl describe service selenium-hub

Then it should be on serviceip:4444 or kube-host:nodeport/

If you need more Firefox or Chrome nodes, your hardware is the limit:

kubectl scale rc selenium-node-firefox --replicas=10
kubectl scale rc selenium-node-chrome --replicas=10

To check on one of the browser nodes via VNC, you may have to proxy depending on your kube setup:

kubectl port-forward -p <POD_NAME> 9000:5900

Then connect to localhost:9000 with your VNC client.

TODO: Figure out healthcheck for the nodes.

Adapted from: https://github.com/SeleniumHQ/docker-selenium

selenium-hub-rc.yaml

apiVersion: v1
kind: ReplicationController
metadata:
  name: selenium-hub 
  labels:
    name: selenium-hub
spec:
  replicas: 1
  selector:
    name: selenium-hub
  template:
    metadata:
      labels:
        name: selenium-hub
    spec:
      containers:
      - name: selenium-hub
        image: selenium/hub:2.47.1 
        ports:
          - containerPort: 4444 
        resources:
          limits:
            memory: "1000Mi"
            cpu: "1"
        livenessProbe:
          httpGet:
            path: /grid/console
            port: 4444
          initialDelaySeconds: 30
          timeoutSeconds: 5
        readinessProbe:
          httpGet:
            path: /grid/console
            port: 4444
          initialDelaySeconds: 30
          timeoutSeconds: 5

selenium-hub-svc.yaml

apiVersion: v1
kind: Service
metadata:
  name: selenium-hub 
  labels:
    name: selenium-hub 
spec:
  ports:
  - port: 4444 
    targetPort: 4444 
    name: port0
  selector:
    name: selenium-hub
  type: NodePort
  sessionAffinity: None

selenium-node-chrome-rc.yaml

apiVersion: v1
kind: ReplicationController
metadata:
  name: selenium-node-chrome 
  labels:
    name: selenium-node-chrome
spec:
  replicas: 3
  selector:
    name: selenium-node-chrome
  template:
    metadata:
      labels:
        name: selenium-node-chrome
    spec:
      containers:
      - name: selenium-node-chrome
        image: selenium/node-chrome-debug:2.47.1
        ports:
          - containerPort: 5900 
        env:
          - name: HUB_PORT_4444_TCP_ADDR 
            value: "selenium-hub"
          - name: HUB_PORT_4444_TCP_PORT 
            value: "4444"
        resources:
          limits:
            memory: "1000Mi"
            cpu: "1"

selenium-node-firefox-rc.yaml

apiVersion: v1
kind: ReplicationController
metadata:
  name: selenium-node-firefox 
  labels:
    name: selenium-node-firefox
spec:
  replicas: 3
  selector:
    name: selenium-node-firefox
  template:
    metadata:
      labels:
        name: selenium-node-firefox
    spec:
      containers:
      - name: selenium-node-firefox
        image: selenium/node-firefox-debug:2.47.1
        ports:
          - containerPort: 5900 
        env:
          - name: HUB_PORT_4444_TCP_ADDR 
            value: "selenium-hub"
          - name: HUB_PORT_4444_TCP_PORT 
            value: "4444"
        resources:
          limits:
            memory: "1000Mi"
            cpu: "1"

Chrome has a known issue running on docker where shm is too small and causes it to crash.

This work around solved it for me /dev/shm:

        resources:
          limits:
            memory: "1000Mi"
            cpu: "1"

          volumeMounts:
            - mountPath: "/dev/shm"
              name: "dshm"

      volumes:
        - name: "dshm"
          emptyDir: 
            medium: "Memory"

How we can share volumes between nodes and hub in kubernetes? I need to download some of the files during the test and that will be accessible from another node.

@hisrarul The best way to share files in Kubernetes is with an object store such as S3 or GCS.