Wrong port is exposed for jaeger-production-query resulting in connection refused

Description of problem:

When deploying Red Hat OpenShift distributed tracing platform with a production strategy the Jaeger query pod can't connect because the service exposes port 16685 When the deployment run on 16686 and 16687.

Version-Release number of selected component (if applicable):

This was tested on 1.39.0-3 with OpenShift Container Platform 4.10 and 4.11

How reproducible:

Every Time

Steps to Reproduce:
1. Install OCP 4.10.x - 4.11.x
2. Follow documentation to install https://docs.openshift.com/container-platform/4.11/distr_tracing/distr_tracing_install/distr-tracing-installing.html
3. Create Jaeger instance with production deployment

Actual results:
Deployment expects ports 16686 and 16687 but service exposes port 16685 and neither of the above

Expected results:

either 16685 needs to be added to the deployment or the service needs to expose the correct ports

Additional info:

attached query log, service yaml, deployment yaml, and jaeger config