WHY

Resolve issue in customer Jira

WHAT
The 3scale DNSByPass Alerts assume that the 3scale routes are exposed on the router-default ingress router. We can't assume this. Instead of using the router-default we need to look up the router used on the appropriate 3scale routes and use that to determine the host and subsequently the IP. 

HOW

current flow:

Here we assume the default ingress router

Then, we get the IP related to the hostname on that router, here

Finally, we ping the endpoint based on the IP, here

new flow:

There are 3 portals to check and therefore 3 routes. For each 3scale route we need to check status.ingress.routerName and pass this to GetIngressRouterService to determine which router to lookup. 

Update the related SOP 

TESTS

Create a custom domain for the cluster ( can use rhmi.me )

Enable an additional router in ocm - see attached. This should correspond to the new custom domain added. We might need to add a label that will ensure that the 3scale routes use this new ingress - needs some investigation. 

Install RHOAM and verify that the 3scale routes are using the new ingress router and verify that no alert are firing. 

Automated tests will capture the default scenario i.e. no custom domain and using the default router.