shorter helm examples

developing-on-openshift/helm/02-first-chart.md

@@ -25,7 +25,7 @@ Our code has been already generated with this command:
 
 Inside `my-chart/` folder you will find these files:
 
-`tree helm/my-chart`{{execute}}
+`tree my-chart`{{execute}}
 
 * `Chart.yaml`{{open}}: is a YAML file containing multiple fields describing the chart
 * `values.yaml`{{open}}:: is a YAML file containing default values for a chart, those may be overridden by users during helm install or helm upgrade.

developing-on-openshift/helm/03-revision.md

@@ -31,7 +31,7 @@ spec:
 
 Run `helm upgrade` to publish a new revision containing a `my-charm` Route:
 
-`helm upgrade my-chart ./helm/my-chart`{{execute}}
+`helm upgrade my-chart ./my-chart`{{execute}}
 
 Verify new `Route` from Terminal:
 
@@ -52,7 +52,7 @@ Verify new `Route` and new `Revision` from Console:
 
 Let's update again our existing release overriding values in `values.yaml` changing `image.pullPolicy` from chart's default value `IfNotPresent` to `Always`, using same method we adopted previously for changing `service.type` with option `--set`:
 
-`helm upgrade my-chart ./helm/my-chart --set image.pullPolicy=Always`{{execute}}
+`helm upgrade my-chart ./my-chart --set image.pullPolicy=Always`{{execute}}
 
 Let's verify that our changes is reflected into resulting `Deployment`:
 
@@ -85,4 +85,4 @@ Verify `imagePullPolicy` is rolled back to `Revision` 2 containing `IfNotPresent
 
 Uninstall will clean everything now, there's no further need to delete manually the `Route` like in first chapter, since the Helm Chart is now managing that resource:
 
-`helm uninstall my-chart`{{execute}}
+`helm uninstall my-chart`{{execute}}

developing-on-openshift/helm/set-env.sh

@@ -2,5 +2,6 @@
 # This is the script to put provisioning things in, this runs in the foreground
 set -o pipefail
 mkdir -p /root/helm/my-chart/charts
+cd /root/helm
 clear
-echo "Helm Tutorial Ready!" 
+echo "Helm Tutorial Ready!"