Ingress Template Silently Overridden by Default Due to Hostname Match

1. Confirm whether the application ingress host matches the existing ingress template host pattern. If the custom ingress hostname matches the template pattern, treat this as expected RTFD behavior where one template may be selected non-deterministically.

2. Change the application URL so it does not match the existing host pattern. For example, given an application name of block-eapi, use blob-eapi2.example instead of the current hostname. 

3. If the existing client URL must be preserved, redeploy the application with a different application name and use the ingress template for the original URL. For example, deploy the application as blob-eapi2 and use the ingress template for blob-eapi.example.com. Note that the application must be deleted and recreated.