📖 running: add note to clarify to push images

- Include additonal note to clarify Rehistry permissions
- Included additional information on RBAC errors with a reference to prerequisites for Kubernetes RBAC on GKE clusters.

 Registry Permission and recommend Kind usage

docs/book/src/cronjob-tutorial/running.md

@@ -74,11 +74,26 @@ make deploy IMG=<some-registry>/<project-name>:tag
 ```
 
 <aside class="note">
-<h1>registry permission</h1>
+<h1>Registry Permission</h1>
 
 This image ought to be published in the personal registry you specified. And it is required to have access to pull the image from the working environment.
 Make sure you have the proper permission to the registry if the above commands don't work.
 
+Consider incorporating Kind into your workflow for a faster, more efficient local development and CI experience.
+Note that, if you're using a Kind cluster, there's no need to push your image to a remote container registry.
+You can directly load your local image into your specified Kind cluster:
+
+```bash
+kind load docker-image <your-image-name>:tag --name <your-kind-cluster-name>
+```
+
+To now more see: [Kind for Dev & CI](./reference/kind.md)
+
+<h1>RBAC errors</h1>
+
+If you encounter RBAC errors, you may need to grant yourself cluster-admin
+privileges or be logged in as admin. See [Prerequisites for using Kubernetes RBAC on GKE cluster v1.11.x and older][pre-rbc-gke] which may be your case.
+
 </aside>
 
 If we list cronjobs again like we did before, we should see the controller