Commits on May 24, 2019

1. Enable registry-proxy …

   As per [this blog](https://blog.hasura.io/sharing-a-local-registry-for-minikube-37c7240d0615) and [this gist](https://gist.github.com/coco98/b750b3debc6d517308596c248daf3bb1), we need to deploy a registry-proxy
   which will expose docker registry on the minikube host.
   
   Once this daemon set is deployed on minikube, one can access registry on `$(minikube ip):5000`.
   This has been tested with minikube v1.0.1 with none driver. With this, one will not have to use
   `kubectl port-forward`. I was able to push a container image to registry using
   ```
   docker push $(minikube ip):5000/test-img
   ```
   And then ran it in minikube using
   ```
   kubectl run -i -t test-img --image=$(minikube ip):5000/test-img --restart=Never
   ```

   

   kumarom committed May 24, 2019
   Configuration menu

   • View commit details
   • Copy full SHA for ec3e7b5
   • Browse repository at this point

   Copy the full SHA

   ec3e7b5 View commit details

   Browse the repository at this point in the history