Merge pull request #11471 from EmandM/patch-1

Update registry.md with instructions to avoid common pitfalls

Author: sharifelgamal

site/content/en/docs/handbook/registry.md

@@ -42,7 +42,8 @@ You can use the `--insecure-registry` flag on the
 
 One nifty hack is to allow the kubelet running in minikube to talk to registries deployed inside a pod in the cluster without backing them
 with TLS certificates. Because the default service cluster IP is known to be available at 10.0.0.1, users can pull images from registries
-deployed inside the cluster by creating the cluster with `minikube start --insecure-registry "10.0.0.0/24"`.
+deployed inside the cluster by creating the cluster with `minikube start --insecure-registry "10.0.0.0/24"`. Ensure the cluster
+is deleted using `minikube delete` before starting with the `--insecure-registry` flag.
 
 ### docker on macOS
 
@@ -53,6 +54,7 @@ The first step is to enable the registry addon:
 ```shell
 minikube addons enable registry
 ```
+> Note: Minikube will generate a port and request you use that port when enabling registry. That instruction is not related to this guide.
 
 When enabled, the registry addon exposes its port 5000 on the minikube's virtual machine.