feat(registry): remove the documentation specifying insecure registry

Author: Keerthan Reddy Mala

src/installing-workflow/system-requirements.md

@@ -26,14 +26,10 @@ application footprint as well.
 Running smaller machines will likely result in increased system load and has been known to result in component failures
 and instability.
 
-## Docker Insecure Registry
+!!! warning
 
-The on-cluster Docker registry is not deployed with TLS enabled. As such, all Kubernetes worker nodes must have their
-Docker daemons configured to use an **insecure registry**. The configured subnet should encompass any private networks
-used by your worker nodes, including overlay networks.
-
-Depending on your Kubernetes and Docker configuration, setting `EXTRA_DOCKER_OPTS="--insecure-registry=10.0.0.0/8"` may
-be sufficient.
+    Versions prior to 2.2 require '--insecure-registry' to function properly. Depending on your Kubernetes and Docker configuration,
+    setting `EXTRA_DOCKER_OPTS="--insecure-registry=10.0.0.0/8"` may be sufficient.
 
 ## SELinux + OverlayFS
 

src/quickstart/provider/aws/boot.md

@@ -51,11 +51,6 @@ LICENSES     README.md    Vagrantfile  cluster/     contrib/     docs/        ex
 Before calling the Kubernetes setup scripts, we need to change a few defaults so that Deis Workflow works best. Type
 each of these commands into your terminal application before calling `kube-up.sh`.
 
-First, enable insecure registry support for Docker:
-```
-$ export KUBE_ENABLE_INSECURE_REGISTRY=true
-```
-
 Next, pick the AWS Availability Zone you would like to use. The boot script will create a new VPC in that region.
 
 ```

src/quickstart/provider/vagrant/boot.md

@@ -39,9 +39,8 @@ LICENSES     README.md    Vagrantfile  cluster/     contrib/     docs/        ex
 Before calling the Kubernetes setup scripts, we need to change a few defaults so that Deis Workflow works best. Type
 each of these commands into your terminal application before calling `kube-up.sh`.
 
-First, enable insecure registry support for Docker and use Vagrant as the provider:
+First, set Vagrant as the provider:
 ```
-$ export KUBE_ENABLE_INSECURE_REGISTRY=true
 $ export KUBERNETES_PROVIDER=vagrant
 ```
 
@@ -57,7 +56,6 @@ Double check the configured environment variables:
 
 ```
 $ env | grep KUBE
-KUBE_ENABLE_INSECURE_REGISTRY=true
 KUBERNETES_PROVIDER=vagrant
 KUBERNETES_NODE_MEMORY=4096
 KUBERNETES_MASTER_MEMORY=1536

src/understanding-workflow/components.md

@@ -93,9 +93,13 @@ configure minio to use persistent storage available in your environment.
 **Project Location:** [deis/registry](https://github.com/deis/registry)
 
 The registry component is a managed docker registry which holds application
-images generated from the builder component. Registry persists the Docker image
-iamges to either local storage (in development mode) or to object storage
-configured for the cluster.
+images generated from the builder component. Registry persists the Docker
+images to either local storage (in development mode) or to object storage
+configured for the cluster. Starting with release v2.2.0, the component also runs a
+[proxy](https://github.com/kubernetes/kubernetes/tree/master/cluster/addons/registry/images)
+daemon to expose the registry service as `localhost` on each node. The proxy daemon uses
+[HAProxy](http://www.haproxy.org/) to route the incoming registry requests on `localhost` to the
+registry service removing the necessity of setting `--insecure-registry` for docker daemon.
 
 ## Router