Selenium Operations: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 10: | Line 10: | ||
x11vnc -usepw -forever -shared -rfbport 5900 -display :99.0 -noxrecord | x11vnc -usepw -forever -shared -rfbport 5900 -display :99.0 -noxrecord | ||
The 5900 port should be exposed by a service similar to: | |||
<syntaxhighlight lang='yaml'> | |||
apiVersion: v1 | |||
kind: Service | |||
metadata: | |||
name: 'selenium-chrome' | |||
spec: | |||
type: LoadBalancer | |||
ports: | |||
- name: 4444-tcp | |||
port: 4444 | |||
targetPort: 4444 | |||
protocol: TCP | |||
- name: 5900-tcp | |||
port: 5900 | |||
protocol: TCP | |||
targetPort: 5900 | |||
selector: | |||
function: 'selenium-chrome' | |||
externalTrafficPolicy: Cluster | |||
</syntaxhighlight> | |||
More details are available here: https://github.com/SeleniumHQ/docker-selenium |
Revision as of 23:58, 17 September 2019
Internal
Connecting to Debug VNC Server
Selenium pods come with an embedded VNC server that allows connection from remote VNC clients.
To check whether the VNC server is running, execute ps, you should see:
x11vnc -usepw -forever -shared -rfbport 5900 -display :99.0 -noxrecord
The 5900 port should be exposed by a service similar to:
apiVersion: v1
kind: Service
metadata:
name: 'selenium-chrome'
spec:
type: LoadBalancer
ports:
- name: 4444-tcp
port: 4444
targetPort: 4444
protocol: TCP
- name: 5900-tcp
port: 5900
protocol: TCP
targetPort: 5900
selector:
function: 'selenium-chrome'
externalTrafficPolicy: Cluster
More details are available here: https://github.com/SeleniumHQ/docker-selenium