Skip to content

K
k3s
Commit 6fc130f7 authored by Kubernetes Submit Queue's avatar Kubernetes Submit Queue Committed by GitHub
Browse files
Options

Merge pull request #41036 from jorahn/patch-1

Automatic merge from submit-queue Docs updated for CLI deprecations **What this PR does / why we need it**: Fixed docs **Release note**: NONE ```release-note ```
parents dfacc61c 9965413d
Hide whitespace changes
Inline Side-by-side
Showing with 4 additions and 4 deletions
examples/selenium/README.md
View file @ 6fc130f7
...@@ -45,7 +45,7 @@ If you cannot reach your Kubernetes nodes from your network, you can proxy via k ...@@ -45,7 +45,7 @@ If you cannot reach your Kubernetes nodes from your network, you can proxy via k
```console ```console
export PODNAME=`kubectl get pods --selector="app=selenium-hub" --output=template --template="{{with index .items 0}}{{.metadata.name}}{{end}}"` export PODNAME=`kubectl get pods --selector="app=selenium-hub" --output=template --template="{{with index .items 0}}{{.metadata.name}}{{end}}"`
kubectl port-forward --pod=$PODNAME 4444:4444 kubectl port-forward $PODNAME 4444:4444
``` ```
In a separate terminal, you can now check the status. In a separate terminal, you can now check the status.
...@@ -79,13 +79,13 @@ Now that the Hub is up, we can deploy workers. ...@@ -79,13 +79,13 @@ Now that the Hub is up, we can deploy workers.
This will deploy 2 Chrome nodes. This will deploy 2 Chrome nodes.
```console ```console
kubectl create --file=examples/selenium/selenium-node-chrome-rc.yaml kubectl create --filename=examples/selenium/selenium-node-chrome-rc.yaml
``` ```
And 2 Firefox nodes to match. And 2 Firefox nodes to match.
```console ```console
kubectl create --file=examples/selenium/selenium-node-firefox-rc.yaml kubectl create --filename=examples/selenium/selenium-node-firefox-rc.yaml
``` ```
Once the pods start, you will see them show up in the Selenium Hub interface. Once the pods start, you will see them show up in the Selenium Hub interface.
...@@ -171,7 +171,7 @@ You now have 10 Firefox and 10 Chrome nodes, happy Seleniuming! ...@@ -171,7 +171,7 @@ You now have 10 Firefox and 10 Chrome nodes, happy Seleniuming!
Sometimes it is necessary to check on a hung test. Each pod is running VNC. To check on one of the browser nodes via VNC, it's recommended that you proxy, since we don't want to expose a service for every pod, and the containers have a weak VNC password. Replace POD_NAME with the name of the pod you want to connect to. Sometimes it is necessary to check on a hung test. Each pod is running VNC. To check on one of the browser nodes via VNC, it's recommended that you proxy, since we don't want to expose a service for every pod, and the containers have a weak VNC password. Replace POD_NAME with the name of the pod you want to connect to.
```console ```console
kubectl port-forward --pod=POD_NAME 5900:5900 kubectl port-forward $POD_NAME 5900:5900
``` ```
Then connect to localhost:5900 with your VNC client using the password "secret" Then connect to localhost:5900 with your VNC client using the password "secret"
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment