We made an error when deploying. Reverting things up. Right now https://infogw-proxy.api.openshift.com/ is down.

Prem: Prem Saraswat:spiral_calendar_pad: 5 minutes ago
I just realised that when I split the previous MR b/w secrets and saas file updates, I forgot to remove the routes update from https://gitlab.cee.redhat.com/service/app-interface/-/merge_requests/21329
This means that infogw-* routes are currently pointing to a non-existent service (token-refresher). There are two solutions:
either get this MR (https://gitlab.cee.redhat.com/service/app-interface/-/merge_requests/21462) merged
or, revert the route change
I'd prefer to get this MR in, but is has the side effect that now infogw-* routes will go through obs API which already has tenant isolation enabled. Since our recording rules are not adding the tenant_id label, users won't be able to query them. @squat any ideas?

https://coreos.slack.com/archives/G79AW9Q7R/p1625049956496600