Was wondering whether I need to hack a custom dialer in my grpc-go implementation, as I'm somewhat of a novice to this.

I've got a setup where you have:

(gRPC) client -> mTLS HTTPS forward proxy -> (gRPC server) public internet

The client presents client certificates to the proxy server over HTTPS and then connects to the final destination. There’s no deep packet inspection, TLS inspection, or SSL bumping.

I saw these GitHub PRs, but neither seems to have been merged yet:

• grpc/grpc#35372

• grpc/grpc-go#6846

• grpc/grpc-java#10453

I tried looking into the official documentation:
grpc-go Proxy Documentation

But it suggests using a custom dialer for use cases not supported by the standard gRPC implementation.