Open gomesar9 opened 3 years ago
The configuration you describe should actually be supported by the operator, so the addition you mention should not be needed.
Just as a sanity check, I assume you have router sharding and that the global routes are picked up only by your router-custom
.
Can you confirm that?
Also do you see anything in the logs regarding the route discovery controller?
Hi, yes the global route may only be assigned to routes labeled, lets say, router: router-custom
and picked up by router-custom
service.
What I mean is, just correctly labeling an application route
, the operator must automatically build a new GlobalDNSRecord
(via GlobalRouteDiscovery
) with:
loadBalancerServiceRef:
name: router-custom
namespace: openshift-ingress
But It's not listed as a configurable spec in GlobalRouteDiscovery
resources. (It seems to be configurable only directly in GlobalDNSRecord
)
Can you confirm this is already possible?
Our running version is: 1.2.0
it should already work, the route discovery operator should correctly populate those fields. Can you attach the following:
may I close this?
Hi all,
we are trying to configure the operator in a cloud infrastructure (AWS) and are facing problems to use custom OCP routes:
We've create a custom service to enable valid HTTPS traffic, with custom certs, through global load balancer and keep our (also valid, not self-signed) cluster certs working.
In this way we can use endpoints from our cluster domain, and use endpoints with a "global" domain, pointing to another Load Balancer, managed by this new service, and configured with the relevant cert/key.
Like:
On
cluster1
:On
cluster-manager
:It works fine, but we loose the Auto Discovery because can not set these parameters in the GlobalRouteDiscovery resource:
Can we have this option? to auto create GlobalDNSRecord with specific router names/namespaces?
Thanks