Hi Lionel, You can always reuse the same data/config dirs and keep your service ips:
oc cluster up --host-data-dir=blah --host-config-dir=blah --use-existing-config > On Aug 7, 2016, at 9:17 PM, Lionel Orellana <lione...@gmail.com> wrote: > > Thanks Clayton. > > Would be nice to have a way of setting the address when using cluster up > though. > On Mon, 8 Aug 2016 at 11:03 AM, Clayton Coleman <ccole...@redhat.com > <mailto:ccole...@redhat.com>> wrote: > When you create the registry you can specify the service IP that is assigned > (as long as another service hasn't claimed it). > > $ oadm registry -o yaml > registry.yaml > $ vi registry.yaml > # Set the registry service `spec.clusterIP` field to a valid service IP > (must be within the service CIDR, typically 172.30.0.0/16 > <http://172.30.0.0/16>) > $ oc create -f registry.yaml > > > On Sun, Aug 7, 2016 at 8:55 PM, Lionel Orellana <lione...@gmail.com > <mailto:lione...@gmail.com>> wrote: > Hi > > I'm facing a similar problem to this: > https://github.com/openshift/origin/issues/7879 > <https://github.com/openshift/origin/issues/7879> > > Basically I need to configure the NO_PROXY variable of the Docker deamon to > include the registry address. Problem is with cluster up I can't control the > ip address that will be assigned to the registry. Or at least I can't find a > way to do it. Is there an option that I'm not seeing? > > Thanks > > Lionel. > > _______________________________________________ > users mailing list > users@lists.openshift.redhat.com <mailto:users@lists.openshift.redhat.com> > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > <http://lists.openshift.redhat.com/openshiftmm/listinfo/users> > > > _______________________________________________ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
