fix: grpc is not running on the ui port

[FauxFaux]

Short description of the changes

all-in-one and jaeger-query do not, in fact, listen for grpc on the same port as http.

If you send grpc requests to this port, you get complete garbage back.

Do not tell people to use the wrong port.

% docker run -it jaegertracing/jaeger-query:1.22 --help  | fgrep -m1 grpc
      --query.grpc-server.host-port string              The host:port (e.g. 127.0.0.1:14250 or :14250) of the query's gRPC server (default ":16685")

Especially relevant as it segfaults if you look at it funny.

[yurishkuro]

Thanks!

I made the change in the next-release file as well.

However, there seem to be more placed that specify -p 16686:1668, they probably all need to be updated?

[yurishkuro]

$ grx 16686:16686 content/docs/1.22
content/docs/1.22/getting-started.md:26:  -p 16686:16686 \
content/docs/1.22/deployment.md:170:  -p 16686:16686 \
content/docs/1.22/deployment.md:565:  -p 16686:16686 \
content/docs/1.22/monitoring.md:47:docker run -e JAEGER_DISABLED=true -p 16686:16686 jaegertracing/all-in-one:{{< currentVersion >}}

[FauxFaux]

Elsewhere the all-in-one docs don't explain the grpc port (even though it's enabled), and don't expose it; just expose the one-ending-in-six, which actually is the UI port and is fine.

We could update all of the docs to tell you to expose all possible ports?