-
Notifications
You must be signed in to change notification settings - Fork 26
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
Proposal feat(controller): allow deis pull from deis-registry #32
Comments
From @deis-admin on January 19, 2017 23:44 From @mboersma on March 26, 2015 22:2 This could also be a use case for |
From @deis-admin on January 19, 2017 23:44 From @babarinde on April 15, 2015 12:40 This s really a needed feature. |
From @deis-admin on January 19, 2017 23:44 From @aledbf on April 15, 2015 12:52 @babarinde the idea of this proposal is to avoid the search of the ip inside the cluster where the registry is running.
yes, just use the ip inside the cluster
that's the idea of deis pull :) (http://deis.io/demo-deis-pull-in-action/)
I don't know if is a "good practice" but for me solves a huge problem (have 1 app as "template" and N "copies", is useful to pull from the cluster without any external connection) |
From @deis-admin on January 19, 2017 23:44 From @babarinde on April 16, 2015 7:23
How does deis resolve example.com:5000 to the internal IP of the registry when the registry is not scaled to 3? |
From @deis-admin on January 19, 2017 23:44 From @aledbf on April 16, 2015 13:9
If you do not specify a full hostname:port Now how deis resolve the registry if there's more than one is the easy part :) |
From @deis-admin on January 19, 2017 23:44
From @aledbf on March 20, 2015 1:7
Something like
to allow the deploy in
application-b
fromapplication-a
without using internal ip addressesCopied from original issue: deis/deis#3341
Copied from original issue: deis/controller#1227
The text was updated successfully, but these errors were encountered: