openwhisk-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [openwhisk-deploy-kube] branch master updated: kind: describe using `kind load` to deploy locally-built image (#536)
Date Thu, 10 Oct 2019 21:26:38 GMT
This is an automated email from the ASF dual-hosted git repository.

dgrove pushed a commit to branch master
in repository

The following commit(s) were added to refs/heads/master by this push:
     new f311016  kind: describe using `kind load` to deploy locally-built image (#536)
f311016 is described below

commit f311016f9bcba7bf8c91aec664c460670479e5b9
Author: David Grove <>
AuthorDate: Thu Oct 10 17:26:33 2019 -0400

    kind: describe using `kind load` to deploy locally-built image (#536)
 docs/ | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)

diff --git a/docs/ b/docs/
index 5b752dc..801321f 100644
--- a/docs/
+++ b/docs/
@@ -112,6 +112,31 @@ we will use the port forwarding configured by the `extraPortMappings`
 in kind-cluster.yaml to allow the OpenWhisk apihost property
 to be set to localhost:31001
+## Hints and Tips
+If you are working on the core OpenWhisk system and want
+to use a locally built controller or invoker image to test
+your changes, you need to push the image to the docker image
+repository inside the `kind` cluster.
+For example, suppose I had a local change to the controller
+I wanted to test.  To do this, I would build the image normally
+(`gradlew distDocker` in `openwhisk`). Then, execute the `kind`
+kind load docker-image whisk/controller
+Then add a stanza to your `mycluster.yaml` to override the default
+behavior of pulling a stable `openwhisk/controller` image from Docker Hub.
+  imageName: "whisk/controller"
+  imageTag: "latest"
+Then deploy OpenWhisk normally using `helm install`. The deployed
+system will use the locally built `whisk/controller` image.
 ## Limitations
 Using kind is only appropriate for development and testing purposes.

View raw message