[images] Determine where we want to push built images for v2 #4

Activity

1. slack

   assigned

   sgoings

   on Nov 12, 2015
2. slack

   added this to the v2.0-alpha1 milestone on Nov 12, 2015
3. rimusz commented on Nov 13, 2015

   

   rimusz

   on Nov 13, 2015

   More actions

   We could use Google Container Registry as our v2 sandbox will be on GKE
4. mboersma commented on Nov 13, 2015

   

   mboersma

   on Nov 13, 2015

   Member

   More actions

   I think it would be confusing to use the existing repo names, even if we host them elsewhere than Docker Hub. My preference would be something like "deis/router-v2:latest" for now, which would eventually just be "deis/router:v2.0.0" when we ship it.

   Also, Deis has been pushing images both to Docker Hub and to quay.io so there is an alternate location, and I think in the future we should continue to do that, at least once we have a release.
5. technosophos commented on Nov 13, 2015

   

   technosophos

   on Nov 13, 2015

   Member

   More actions

   I feel like it might politically be in our best interest to not host Kubernetes-focused images on DockerHub. Solomon expressed his feelings about that on Twitter (directed at me) a few days ago. But I'll defer to @sgoings on what place is best.
6. rimusz commented on Nov 13, 2015

   

   rimusz

   on Nov 13, 2015

   More actions

   so we have two options left the Google Container Registry or quay.io :)
   quay.io has an advantage that it supports rkt images but for the start GCR could be a better option, as it is quicker to work with.
   quay.io is not so quick to use from Europe :(
7. sgoings commented on Nov 13, 2015

   

   sgoings

   on Nov 13, 2015

   Member

   More actions

   We will probably have our CI system and release process pushing out identical images to all 3. We'll start with just pushing to Docker Hub unless we deal with consistent image push problems... then we can re address.
8. bacongobbler commented on Dec 3, 2015

   

   bacongobbler

   on Dec 3, 2015

   Member

   More actions

   I think we've finally determined this, and we are using travis to push to both quay and dockerhub.
9. bacongobbler

   closed this as completedon Dec 3, 2015
10. duanhongyi

    added a commit that references this issue on Dec 4, 2018

    Merge pull request deis#4 from dtzar/acs-quickstart

    ...

    205f571