This is an automated email from the ASF dual-hosted git repository.
dgrove pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/openwhisk-deploy-kube.git
The following commit(s) were added to refs/heads/master by this push:
new 890338d Updated to include Windows tools (#650)
890338d is described below
commit 890338dcf37500c00460aa2bc40ad863a9c0d935
Author: Erdogan Kurtur <[email protected]>
AuthorDate: Tue Oct 27 17:03:51 2020 +0300
Updated to include Windows tools (#650)
Instead of `grep` which is not deployed with Windows by default, converted
code to use built-in `find` tool.
Also added a step to reduce possible installation issues
---
docs/k8s-docker-for-windows.md | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/docs/k8s-docker-for-windows.md b/docs/k8s-docker-for-windows.md
index 8fbf06d..d511001 100644
--- a/docs/k8s-docker-for-windows.md
+++ b/docs/k8s-docker-for-windows.md
@@ -60,7 +60,7 @@ the box to enable Kubernetes.
### Configuring OpenWhisk
You will be using a NodePort ingress to access OpenWhisk. Assuming
-`kubectl describe nodes | grep InternalIP` returns 192.168.65.3 and
+`kubectl describe nodes | find "InternalIP"` returns 192.168.65.3 and
port 31001 is available to be used on your host machine, a
mycluster.yaml for a standard deployment of OpenWhisk would be:
@@ -77,6 +77,10 @@ nginx:
### 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:
