Hi Peter,
We have the same case in one of our OpenShift deployments. We decided to
experiment with router sharding.
https://blog.openshift.com/openshift-router-sharding-for-production-and-development-traffic/
On 8/30/18 3:07 PM, David Conde wrote:
Hi Peter,
Hopefully
https://docs.openshift
Hi Peter,
Hopefully
https://docs.openshift.com/container-platform/3.9/architecture/networking/routes.html#whitelist
will sort you out.
Dave
On Thu, Aug 30, 2018 at 1:54 PM Peter Heitman wrote:
> In my deployment there are 5 routes - two of them are from OpenShift
> (docker-registry and registr
works 😊
François
De : users-boun...@lists.openshift.redhat.com
De la part de Peter Heitman
Envoyé : jeudi 30 août 2018 14:54
À : users@lists.openshift.redhat.com
Objet : Restricting access to some Routes
In my deployment there are 5 routes - two of them are from OpenShift
(docker-registry and
In my deployment there are 5 routes - two of them are from OpenShift
(docker-registry and registry-console) and three of them are specific to my
application. Of the 5, 4 of them are administrative and shouldn't be
accessed by just anyone on the Internet. One of my application's route is
required to
