[Feature] [OAP] Combining HTTP and gRPC on a Single Port through Armeria about skywalking HOT 4 OPEN

What's the scope of this issue, does it aim at combining the HTTP and gRPC of the telemetry collecting endpoints (11800 and 12800), or does it also include other HTTP/gRPC protocols such as otel collector or Zipkin endpoints?

from skywalking.

I want to unify the stack and reduce the confusion of users about which port to use, but to keep compatibility, all existing port should be kept.

So 11800 and 12800 should share the HTTP and gRPC. 11800 will become the primary port, and 12800 as secondary port.
Meanwhile, as Zipkin port should keep to handle HTTP traffic only.

WDYT?

from skywalking.

I want to unify the stack and reduce the confusion of users about which port to use, but to keep compatibility, all existing port should be kept.

So 11800 and 12800 should share the HTTP and gRPC. 11800 will become the primary port, and 12800 as secondary port. Meanwhile, as Zipkin port should keep to handle HTTP traffic only.

WDYT?

Sounds reasonable, I've been thinking of reducing the ports we used, one reason stops me to do so is that, different ports has different functionality and for sake of security, users need to configure different security policies for different ports, for example, 11800 may be internally accessible only inside data center but 12800 may need to be accessible in end user's browser, it may be still possible to configure different security policies after combining the ports but it is foreseeably more complex.

from skywalking.

If consider keeping security controllable, we just make receiver port unified and query separately.

This should be better?

query port and receiver port and core port for internal communications.

from skywalking.