You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openwhisk.apache.org by ra...@apache.org on 2018/05/03 19:41:33 UTC

[incubator-openwhisk-deploy-kube] branch master updated: add pointer to Helm deployment to top-level README.md (#189)

This is an automated email from the ASF dual-hosted git repository.

rabbah pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-openwhisk-deploy-kube.git


The following commit(s) were added to refs/heads/master by this push:
     new 241eac9  add pointer to Helm deployment to top-level README.md (#189)
241eac9 is described below

commit 241eac9135a7488f4d38cb30d9fd381362401f35
Author: David Grove <dg...@users.noreply.github.com>
AuthorDate: Thu May 3 15:41:30 2018 -0400

    add pointer to Helm deployment to top-level README.md (#189)
---
 README.md      |  8 ++++++++
 helm/README.md | 14 +++++++++++++-
 2 files changed, 21 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index d89c762..08e1ad7 100644
--- a/README.md
+++ b/README.md
@@ -110,6 +110,14 @@ kubectl delete namespace openwhisk
 kubectl delete persistentvolume -lpv-owner=openwhisk
 ```
 
+# Deploying OpenWhisk using Helm
+
+We are also working on developing Helm charts to deploy OpenWhisk on
+Kubernetes. Currently, the Helm charts do not support all of the
+configuration options of the more manual deployment process described
+above. However, they are sufficient for deploying the core OpenWhisk
+system on Minikube. Please see [helm/README.md](helm/README.md) for more details.
+
 # Issues
 
 Report bugs, ask questions and request features [here on GitHub](../../issues).
diff --git a/helm/README.md b/helm/README.md
index 6389115..bbe4a83 100644
--- a/helm/README.md
+++ b/helm/README.md
@@ -59,10 +59,22 @@ $ kubectl label nodes <INVOKER_NODE_NAME> openwhisk-role=invoker
 ```
 
 ### Step 4. Deploy Charts
+You will need to create a mycluster.yaml file that specifies the host
+and port information that will be used to access your cluster.  See
+the [ingress discussion](../kubernetes/ingress/README.md) for
+details. Below is a sample file appropriate for a minikube cluster
+where `minikube ip` returns `192.168.99.100`.
+
+```yaml
+whisk:
+  ingress:
+    api_host: 192.168.99.100:31001
+    apigw_url: 192.168.99.100:31004
+```
 
 Deployment can be done by using the following single command:
 ```shell
-helm install . --namespace=openwhisk --name=your_release_name
+helm install . --namespace=openwhisk --name=your_release_name -f mycluster.yaml
 ```
 
 After a while, if you can see all the pods listed by the following command are in `Running` state, congratulations, you have finished OpenWhisk deployment:

-- 
To stop receiving notification emails like this one, please contact
rabbah@apache.org.