[GitHub] [openwhisk-deploy-kube] chetanmeh commented on a change in pull request #536: kind: describe using `kind load` to deploy locally-built image

[GitBox <gi...@apache.org>]

chetanmeh commented on a change in pull request #536: kind: describe using `kind load` to deploy locally-built image
URL: https://github.com/apache/openwhisk-deploy-kube/pull/536#discussion_r332466213
 
 

 ##########
 File path: docs/k8s-kind.md
 ##########
 @@ -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`
+command
+```shell
+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.
+```yaml
+controller:
+  imageName: "whisk/controller"
+  imageTag: "latest"
+```
+
+Then deploy OpenWhisk normally using `helm install`. The deployed
 
 Review comment:
   Should we document using `helm upgrade --install` instead of install for incremental deployment to avoid creating new release and just refresh the existing controller/invoker?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services