Update README.md

Updated to consistently use namespace px-bench (for now!)

README.md

@@ -12,12 +12,13 @@ docker push ...
 * Create a namespace for your benchmarking, and set your context to it (or ensure that you are applying all YAML below to that namespace)
 * TBD: Create a wrapper script that will create the namespace and apply all YAML in order and with correct timing!
 * Copy an example `px-bench-env.yml` from the examples directory. There are various examples for different clound enviroments.
+* Create the px-bench namespace with `kubectl create ns px-bench`
 * Edit `px-bench-env.yml` to set the ConfigMap `env` to set desired values. If necessary, update `image:` to reflect the image you built.
-* `kubectl apply -f px-bench.yml` to start apply the configuration settings.
+* `kubectl -n px-bench apply -f px-bench-env.yml` to start apply the configuration settings.
 * Do NOT edit `px-bench-main.yml` (unless you are attempting to change the behavior of the benchmark!)
-* In order to consume most of the available RAM so it is not used for buffering, run `kubectl apply -f chewram.yml`.
-* Wait for `kubectl get pod -n chewram` for all the pods to show as `1/1 Running`.
-* `kubectl apply -f px-bench.yml` to start the run.
+* In order to consume most of the available RAM so it is not used for buffering, run `kubectl -n px-bench apply -f chewram.yml`.
+* Wait for `kubectl -n px-bench get pod -n chewram` for all the pods to show as `1/1 Running`.
+* `kubectl -n px-bench apply -f px-bench.yml` to start the run.
 * Monitor its progress with `kubectl logs -n px-bench -l px-bench=fio -f`. With the defaults, runtime is expected to be around 15 minutes.
 * Wait for `kubectl get pod -n px-bench` for all the pods to show as Completed.