Add create/delete registry flag to kind doc
@@ -21,25 +21,48 @@ You can proceed to create clusters once you have `kind` available in your path.
The `NUM_CLUSTERS` is `2` by default. Set that variable before invoking the
script if you'd like to change the default.
-### Configure Insecure Container Registry
+### Create Insecure Container Registry
-Please answer the following questions to determine if you need to set up an
+Please answer the following question to determine if you need to set up an
insecure container registry on your host:
-1. Is this the first time you're running the `create-clusters.sh` script?
-2. Are you planning on creating container images locally without pushing to a
+1. Are you planning on creating container images locally without pushing to a
public container registry such as quay.io?
-If you answered yes to both of these questions, then you will need to
-configure the docker daemon on your host for an insecure container registry.
-Configuring a container registry is necessary if you want your kind clusters to
-pull images that you built locally on your host without pushing them to a
-public container registry. The reason for an insecure registry is to simplify
-the container registry setup by not enabling TLS. See the [docker
+If you answered yes, then you will need to create an insecure container
+registry. Creating a container registry is necessary if you want your kind
+clusters to pull images that you built locally on your host without pushing
+them to a public container registry. See the [docker
docs](https://docs.docker.com/registry) for more details.
+In order to create an insecure container registry, you can pass the
+`CREATE_INSECURE_REGISTRY` flag to `create-clusters.sh` as follows:
+
+```bash
+CREATE_INSECURE_REGISTRY=y ./scripts/create-clusters.sh
+```
+
+### Configure Insecure Container Registry
+
+Please answer the following questions to determine if you need to configure an
+insecure container registry on your host:
+
+1. Is this the first time you're running the `create-clusters.sh` script?
+2. Does your docker daemon need to be configured for an insecure container
+ registry?
+
+If you answered yes to both of these questions, then you will need to configure
+the docker daemon on your host for an insecure container registry. The reason
+for an insecure registry is to simplify the container registry setup by not
+enabling TLS. **This only needs to be done once for a particular host**.
+See the [docker docs](https://docs.docker.com/registry) for more details.
+
In order to configure an insecure container registry, you can pass the
-`CONFIGURE_INSECURE_REGISTRY` flag to `create-clusters.sh` as follows:
+`CONFIGURE_INSECURE_REGISTRY` flag to `create-clusters.sh` as shown below. The
+default container registry host is `172.17.0.1:5000` and needs to match
+the IP address of the default docker bridge on your host, typically
+`172.17.0.1`. If you would like to change this then set the
+`CONTAINER_REGISTRY_HOST="<host>:<port>"` flag.
```bash
CONFIGURE_INSECURE_REGISTRY=y ./scripts/create-clusters.sh
@@ -64,9 +87,21 @@ Run the following command to create `2` `kind` clusters:
## Delete Clusters
-Run the following command to delete your `2` `kind` clusters. If you've
-specified a different `NUM_CLUSTERS` than the default, make sure to set it
-again before invoking the script.
+The NUM_CLUSTERS is 2 by default. Set that variable before invoking the script
+if you'd like to change the default.
+
+### Delete Insecure Container Registry
+
+Specify the `DELETE_INSECURE_REGISTRY` flag if you set up an insecure container
+registry and would like to have it deleted.
+
+```bash
+DELETE_INSECURE_REGISTRY=y ./scripts/delete-clusters.sh
+```
+
+### Run Script
+
+Run the following command to delete `2` `kind` clusters:
```bash
./scripts/delete-clusters.sh
