Presented at the Amsterdam Kubernetes Addicts Meetup https://www.meetup.com/Kubernetes-Addicts-Support-Group

1. container-solutions.com etienne.tremel@container-solutions.com Selenium Hub on Kubernetes @etiennetremel
info@container-solutions.com
container-solutions.com
Selenium
Hub on
Kubernetes
Etienne Tremel
etienne.tremel@container-solutions.com
@etiennetremel

2. container-solutions.com etienne.tremel@container-solutions.com Selenium Hub on Kubernetes @etiennetremel
Lint
E2E in CI/CD pipeline
Build
Deploy
Acceptance
Deploy
Production
Unit tests
Merge
E2E tests

3. container-solutions.com etienne.tremel@container-solutions.com Selenium Hub on Kubernetes @etiennetremel
Selenium Hub overview
HUB
Chrome
Node
Firefox
Node

4. container-solutions.com etienne.tremel@container-solutions.com Selenium Hub on Kubernetes @etiennetremel
Install
Simple install
$ helm upgrade -i selenium stable/selenium
Custom version
$ helm upgrade -i selenium
--set chrome.enabled=true
--set chrome.tag=3.7.1
--set firefox.enabled=true
stable/selenium

5. container-solutions.com etienne.tremel@container-solutions.com Selenium Hub on Kubernetes @etiennetremel
Debug
Debug:
$ helm upgrade -i selenium
--set chromeDebug.enabled=true
--set firefoxDebug.enabled=true
stable/selenium
Port-forward, connect to client using VNC on localhost:5900 :
$ kubectl port-forward $(kubectl get pods
-l app=selenium-selenium-chrome-debug
-o jsonpath='{ .items[0].metadata.name }') 5900

6. container-solutions.com etienne.tremel@container-solutions.com Selenium Hub on Kubernetes @etiennetremel
SeleniumHub overview

7. container-solutions.com etienne.tremel@container-solutions.com Selenium Hub on Kubernetes @etiennetremel
SeleniumHub on Minikube
kind: Service
apiVersion: v1
metadata:
name: wct
spec:
ports:
- protocol: TCP
port: 8081
targetPort: 8081
kind: Endpoints
apiVersion: v1
metadata:
name: wct
subsets:
- addresses:
- ip: 10.0.2.2
ports:
- port: 8081

8. container-solutions.com etienne.tremel@container-solutions.com Selenium Hub on Kubernetes @etiennetremel
- Only Chrome and Firefox with fixed version
- Session hangs, mostly on Firefox
- Session doesn’t get killed correctly causing nodes to be unavailable
- Flaky tests, need to implement retry mechanism
- Need to implement your own autoscaler based on the hub queue
Fully managed solutions:
- BrowserStack
- SauceLab
- Xamarin?
To conclude