he customer wanted to add the TLS certificate generated by their enterprise CA to the route "migration" in the `openshift-migration` project.

Based on the internal discussion mentioned customer that he can probably just add the certs to the existing route migration, the operator would not overwrite them. As long as the customer doesn't touch other fields the operator is explicitly setting by applying the template it won't muck with it. Link [1] explains how to add custom certificates to the custom edge routes

[1]https://docs.openshift.com/container-platform/4.11/networking/routes/secured-routes.html#nw-ingress-creating-an-edge-route-with-a-custom-certificate_secured-routes

The customer mentioned that the above workaround suggested worked.

Since the above workaround basically requires editing objects managed by an operator, the customer wants an RFE that we could just mention a secret containing a cert inside the migration-controller CR to achieve this.
~~~
$ oc get routes -n openshift-migration
NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD
discovery discovery-openshift-migration.apps.dev-intranet-10-wob.ocp.vwgroup.com discovery <all> edge/Redirect None
migration migration-openshift-migration.apps.dev-intranet-10-wob.ocp.vwgroup.com migration-ui port-9000 edge/Redirect None
~~~

Slack discussion Link:
https://redhat-internal.slack.com/archives/CFN0XJEPR/p1687739978544239