From 4a0e871e89f4a9b195ff0ed48becd089981ed9ff Mon Sep 17 00:00:00 2001
From: Gustavo Massaneiro <gustavomassa123@gmail.com>
Date: Tue, 21 Dec 2021 16:36:39 -0300
Subject: [PATCH] Updated Standard Development Workflow

---
 Development-Workflows.md | 19 +++++++++++++++++--
 1 file changed, 17 insertions(+), 2 deletions(-)

diff --git a/Development-Workflows.md b/Development-Workflows.md
index 43fd62d..4a8f954 100644
--- a/Development-Workflows.md
+++ b/Development-Workflows.md
@@ -11,13 +11,28 @@ Whenever you make changes in the `agent` and `tap` packages or protocol extensio
 $ docker build . -t example/mizuagent:latest
 ```
 
-Then you need to push that image into Docker Hub:
+If you are using minikube, you can use the locally built image instead of pushing the image to Docker hub:
+
+```shell
+$ minikube image load example/mizuagent:latest
+```
+
+If you are using a real kubernetes cluster, you need to push the image into Docker Hub:
 
 ```shell
 $ docker push example/mizuagent:latest
 ```
 
-Set the `agent-image` to `example/mizuagent:latest` in the Mizu config YAML (on path `~/.mizu/config.yaml`):
+If you are using minikube, set the `agent-image` to `example/mizuagent:latest` and also set the `image-pull-policy` to `Never` in the Mizu config YAML (on path `~/.mizu/config.yaml`):
+
+```shell
+user@Machine:~/.mizu$ cat config.yaml
+image-pull-policy: Never
+agent-image: example/mizuagent:latest
+telemetry: false
+```
+
+If you are using a real kubernetes cluster, set the `agent-image` to `example/mizuagent:latest` in the Mizu config YAML (on path `~/.mizu/config.yaml`):
 
 ```shell
 user@Machine:~/.mizu$ cat config.yaml