github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-29 06:27:05 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #41036 from jorahn/patch-1

Browse Source 
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
```
This commit is contained in:
Kubernetes Submit Queue 2017-02-20 11:22:32 -08:00 committed by GitHub
commit 6fc130f799
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
examples/selenium/README.md
View File

@ -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.
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!
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"