Docs updated for CLI deprecations

examples/selenium/README.md

@@ -45,7 +45,7 @@ If you cannot reach your Kubernetes nodes from your network, you can proxy via k
 
 ```console
 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.
@@ -79,13 +79,13 @@ Now that the Hub is up, we can deploy workers.
 This will deploy 2 Chrome nodes.
 
 ```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.
 
 ```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.
@@ -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.
 
 ```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"