APIcast integration with Jaeger in another project, namespace

This steps to Installing Jaeger show Jaeger being installed in the same project as 3scale. Jaeger can be run in a separate project/namespace with the following changes to jaeger_config.json shown in the documentation.

• change "hostPort" : "127.0.0.1:5778"
  to "hostPort" : "jaeger-agent.logs.svc.cluster.local:5778",

• change "localAgentHostPort" : "jaeger-agent:6831"
  to "localAgentHostPort" : "jaeger-agent.logs.svc.cluster.local:-5778-6831"

This has been done by a customer. I have verified it my own local instance.
I am creating this task for QE (who tests in the same namespace for simplicity) and eloycoto to verify/confirm there are no issues with the above.