In the future we've discussed having a separate "who owns this 'name' policy" which would allow us to relax this, where you'd get checked whenever you tried to use a name that spans multiple namespaces. Hasn't happened yet though.
On Thu, Jun 15, 2017 at 10:07 AM, Jessica Forrester <[email protected]> wrote: > For routes, this is not a limitation of the GUI, it is an intentional > limitation of the platform. You can't change your hostname because the > router needs a way to decide which route wins when multiple routes ask for > the same hostname. Right now this is done based on age of the route > (oldest wins). If you changed your hostname on an old route, you could > steal someone else's hostname they had previously been granted. Hence the > requirement that you create a new route if you need a new hostname. If > there are any plans to change how this is done the networking team would > need to chime in. Note: the exception is that a cluster admin is allowed > to change the hostname on a route > > For authenticating to git servers, have you seen this feature: > https://blog.openshift.com/wp-content/uploads/wn34-3-secret-editor.gif > Originally added as part of 3.4 https://blog.openshift.com > /whats-new-in-openshift-3-4-enhanced-usability/ > > > On Wed, Jun 14, 2017 at 5:57 PM, Louis Santillan <[email protected]> > wrote: > >> With regards to routes, the best thing to do is create a new route that >> matches the DNS name you want. >> >> ----------------------------------------------------------------------- >> >> LOUIS P. SANTILLAN >> >> SENIOR CONSULTANT, OPENSHIFT, MIDDLEWARE & DEVOPS >> >> Red Hat Consulting, NA US WEST <https://www.redhat.com/> >> >> [email protected] M: 3236334854 >> <https://red.ht/sig> >> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >> >> On Wed, Jun 14, 2017 at 2:42 PM, Hetz Ben Hamo <[email protected]> wrote: >> >>> Hi, >>> >>> I was wondering regarding the GUI of openshift if the following features >>> are planned (or available): >>> >>> 1. Change the route DNS name after it has been already created (I think >>> it's available on the hosted openshift, but not on origin). >>> 2. A simpler way to authenticate to GIT based solution (Gitlabs, >>> internal Git server). A simpler I mean a way to click a checkbox to select >>> authentication method and type user,pass. >>> >>> Thanks >>> >>> _______________________________________________ >>> users mailing list >>> [email protected] >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >>> >>> >> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> >> > > _______________________________________________ > users mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
