SteveD1979 The issue here is that you have 2 different pieces handling two different parts of your request.
1. The GTM will resolve all DNS requests it is sent. 2. After you have DNS resolve you then have your request directly to the destination IP that the GTM pointed you to for lets say application1.example.com. This part of the request is not something the GTM would see because it is an application request and not a DNS request. The GTM doesn't change the original FQDN that you are attempting to resolve a destination for.
Right i wanted to put an irule or policy on the VIP on the LTMs to redirect it from the gtm.domain.com name to the datacenter.domain.com name that it's expecting but keep the part of the URL that is wildcarded so that openshift would know where to send it.
DNS record currently *.datacenter.domain.com = VIP on LTM for openshift router with several applications hitting it.
DNS record desired for developers to use = theirapplication.gtm.domain.com
Route currently openshift is configured to recognize = theirapplication.datacenter.domain.com
SteveD1979 Your developers should not be using the FQDN of theirapplication.gtm.example.com they should be using theirapplication.example.com. Please take a moment to look at the two images that explains a little on what is happening when the developers make a query for their app and how DNS should be configured so that the GTM is used appropriately to minimize what the client sees. Pay close attention to what comes back in DNS and what the client uses to make the application request.
I understand that but it would still be the same scenerio. I just wanted to see if it would be possible to rewrite a portion of the URL. If not I'm going to have get our openshift engineer to just add this route. Nothing was settled on yet the URL the devs use could be just application.domain.com but i would still need to flip it to what openshift is expecting as the route
SteveD1979 In order to understand this a bit better could you go into a bit more detailed explanation of Openshift? From what I can tell Openshift has a list of applications and their respective FQDN match. So in this list if they the following I am still failing to see the issue.
If you have to hardcode the destination IP for each app then I can see why you might have an issue but other than that I'm not sure why this is an issue. If I'm incorrect in my assumption please provide some additional detail on how openshift application references function.