text stringlengths 0 59.1k |
|---|
labels: |
app: selenium-hub |
spec: |
replicas: 1 |
selector: |
matchLabels: |
app: selenium-hub |
template: |
metadata: |
labels: |
app: selenium-hub |
spec: |
containers: |
- name: selenium-hub |
image: selenium/hub:4.0 |
ports: |
- containerPort: 4444 |
- containerPort: 4443 |
- containerPort: 4442 |
resources: |
limits: |
memory: "1000Mi" |
cpu: ".5" |
livenessProbe: |
httpGet: |
path: /wd/hub/status |
port: 4444 |
initialDelaySeconds: 30 |
timeoutSeconds: 5 |
readinessProbe: |
httpGet: |
path: /wd/hub/status |
port: 4444 |
initialDelaySeconds: 30 |
timeoutSeconds: 5 |
<|endoftext|> |
# source: k8s_examples/_archived/selenium/selenium-node-chrome-deployment.yaml type: yaml |
apiVersion: apps/v1 |
kind: Deployment |
metadata: |
name: selenium-node-chrome |
labels: |
app: selenium-node-chrome |
spec: |
replicas: 2 |
selector: |
matchLabels: |
app: selenium-node-chrome |
template: |
metadata: |
labels: |
app: selenium-node-chrome |
spec: |
volumes: |
- name: dshm |
emptyDir: |
medium: Memory |
containers: |
- name: selenium-node-chrome |
image: selenium/node-chrome:4.0 |
ports: |
- containerPort: 5555 |
volumeMounts: |
- mountPath: /dev/shm |
name: dshm |
env: |
- name: SE_EVENT_BUS_HOST |
value: "selenium-hub" |
- name: SE_EVENT_BUS_SUBSCRIBE_PORT |
value: "4443" |
- name: SE_EVENT_BUS_PUBLISH_PORT |
value: "4442" |
resources: |
limits: |
memory: "1000Mi" |
cpu: ".5" |
<|endoftext|> |
# source: k8s_examples/_archived/selenium/README.md type: docs |
## Selenium on Kubernetes |
Selenium is a browser automation tool used primarily for testing web applications. However when Selenium is used in a CI pipeline to test applications, there is often contention around the use of Selenium resources. This example shows you how to deploy Selenium to Kubernetes in a scalable fashion. |
### Prerequisites |
This example assumes you have a working Kubernetes cluster and a properly configured kubectl client. See the [Getting Started Guides](https://kubernetes.io/docs/getting-started-guides/) for details. |
Google Container Engine is also a quick way to get Kubernetes up and running: https://cloud.google.com/container-engine/ |
Your cluster must have 4 CPU and 6 GB of RAM to complete the example up to the scaling portion. |
### Deploy Selenium Grid Hub: |
We will be using Selenium Grid Hub to make our Selenium install scalable via a master/worker model. The Selenium Hub is the master, and the Selenium Nodes are the workers(not to be confused with Kubernetes nodes). We only need one hub, but we're using a replication controller to ensure that the hub is always running: |
```console |
kubectl create --filename=staging/selenium/selenium-hub-deployment.yaml |
``` |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.