document installing release using Helm repository (#671)
diff --git a/README.md b/README.md
index 837e6a3..3ac083b 100644
--- a/README.md
+++ b/README.md
@@ -243,16 +243,33 @@
You can use a different name and/or namespace simply by changing the commands
used below.
-**NOTE:** Clone the repository https://github.com/apache/openwhisk-deploy-kube.git and use to Helm chart available under the `helm/openwhisk` folder.
+**NOTE:** The commands below assume Helm v3.2.0 or higher. Verfiy your local Helm version with the command `helm version`.
-Deployment can be done by using the following single command:
+### Deploying Released Charts from Helm Repository
+
+The OpenWhisk project maintains a Helm repository at `https://openwhisk.apache.org/charts`.
+You may install officially released versions of OpenWhisk from this repository:
+
+```
+helm repo add openwhisk https://openwhisk.apache.org/charts
+helm repo update
+helm install owdev openwhisk/openwhisk -n openwhisk --create-namespace -f mycluster.yaml
+```
+
+### Deploying from Git
+
+To deploy directly from sources, either download the
+[latest source release](https://github.com/apache/openwhisk-deploy-kube/releases) or
+`git clone https://github.com/apache/openwhisk-deploy-kube.git` and use the Helm chart
+from the `helm/openwhisk` folder of the sourc tree.
+
```shell
helm install owdev ./helm/openwhisk -n openwhisk --create-namespace -f mycluster.yaml
```
-**NOTE:** The above command will only work for Helm v3.2.0 or higher versions. Verfiy your local Helm version with the command `helm version`.
+### Deploying to OKD/OpenShift
-Deploying to OKD/OpenShift uses the command sequence:
+Deploying to OKD/OpenShift currently requires a two command sequence:
```shell
helm template owdev ./helm/openwhisk -n openwhisk -f mycluster.yaml > owdev.yaml
oc create -f owdev.yaml
@@ -262,6 +279,8 @@
We recommend generating to a file to make it easier to undeploy OpenWhisk later
by simply doing `oc delete -f owdev.yaml`
+### Checking status
+
You can use the command `helm status owdev -n openwhisk` to get a summary
of the various Kubernetes artifacts that make up your OpenWhisk
deployment. Once the pod name containing the word `install-packages` is in the `Completed` state,
diff --git a/docs/k8s-docker-for-windows.md b/docs/k8s-docker-for-windows.md
index d511001..8296990 100644
--- a/docs/k8s-docker-for-windows.md
+++ b/docs/k8s-docker-for-windows.md
@@ -77,10 +77,6 @@
### Using helm to install OpenWhisk
-Installation expects `openwhisk` namespace to be created. To create, run
-
-`kubectl create namespace openwhisk`
-
Indicate the Kubernetes worker nodes that should be used to execute user
containers by OpenWhisk's invokers. For a single node development cluster,
simply run:
@@ -92,7 +88,7 @@
```cmd
cd openwhisk-deploy-kube
-helm install owdev ./helm/openwhisk -n openwhisk -f mycluster.yaml
+helm install owdev ./helm/openwhisk -n openwhisk --create-namespace -f mycluster.yaml
```
You can use the command `helm status owdev -n openwhisk` to get a summary of the various
