Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable registry-proxy #4341

Merged
merged 1 commit into from
May 28, 2019
Merged

Enable registry-proxy #4341

merged 1 commit into from
May 28, 2019

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
    Copy the full SHA
    ec3e7b5 View commit details
    Browse the repository at this point in the history