(Red Hat OpenShift) Determining routes for service access
After you configure and deploy your containers, you can use OpenShift Cloud Platform to determine the routes you use to access the services in your content services environment.
About this task
As of IBM Cloud Pak® for Business Automation 21.0.3, most traffic, by default, goes through the Cloud Pak Platform UI(Zen) front door. Clients of CP4BA applications need to use a URL that goes through the Zen front door route followed by an application-specific prefix.
The Zen front door route can be determined by running the command: oc get route |grep cpd
|awk '{print $2}'. Using the Zen front door has several implications, which include the
application URLs, HTTP response headers, and authentication. The Zen URL for IBM Business Automation Navigator is
https://<Zen_front_door_route>/icn/navigator.
You can also use the legacy route URL to access. The legacy route can be determined by running
the command: oc get route |grep navigator |awk '{print $2}'. The legacy URL route
for IBM Business Automation Navigator is
https://<legacy_route>/navigator.
If an application is looking for a load-balancing pattern that uses round-robin where session affinity is not enforced, then the Zen route that contains the application prefix that is shown in the previous table can be used or a non-Zen route that is named with 'stateless' can be used.
If an application needs session affinity, it cannot use the Zen route. Instead, it uses the routes without the 'stateless' in the name. This ensures that the load balancing for the back-end services provides for sticky session affinity based on the client IP.
You can find these routes in the xxx-access-info configmap. For more
information, see Option 2: Installing a production deployment in the OpenShift console.
To determine your routes, you can use either the console settings or the command line.
Procedure
To determine your service routes: