Improve gRPC support

[emmanuelbernard]

Clement internal wish: Quarkus 1.7 / 1.8

• - Add support for compressor #9324 - Compressor support
• - Add support for name resolver #9325 - Name resolver support
• - Add support for load balancers #9326 - Load balancer support
• - Add interceptor to enable hot reload on incoming gRPC requests #9327 - hot reload on RPC request
• - Improve developer experience and hot reload support #9328 - hot reload on proto file change
• - Proper implementation of the back pressure protocol #9329 - control flow integration

[emmanuelbernard]

@michalszynkiewicz @cescoffier let's write down what that means and what value this brings.

[cescoffier]

• Hot reload support (even when modifying the proto file)
• Compressor support
• Proper implementation of the back-pressure protocol
• load-balancer support

[michalszynkiewicz]

What about e.g. load balancer support?

[cescoffier]

Yes, let me add that too.

[cescoffier]

I've added in the issue description the individual issues.

[parkee]

I noticed currently grpc calls don't propagate tracing context (jaeger or b3 headers).
I suppose that also should be added to the list of improvements.

Is there a way to work around that at this time and manually add support for tracing?

[michalszynkiewicz]

@pavolloffay what do you think about tracing context for grpc calls ^

[pavolloffay]

+1

[michalszynkiewicz]

@parkee could you create an issue and we will discuss with @cescoffier when he's back from PTO if we want it here or separately?

[parkee]

Sure @michalszynkiewicz
#11059

[n1hility]

@michalszynkiewicz @cescoffier should we split this issue into 1.8 and 1.9? It looks like we aren't going to get to everything in time for 1.8

[cescoffier]

The remaining issues are mostly going to be 1.9 / 1.10.

[cescoffier]

@michalszynkiewicz do you prefer keeping this epic or create individual issues?

[michalszynkiewicz]

we already have individual tasks, don't we?
I'm okay with closing this, I'm focusing on tasks anyway.