4 ms·
Yes, I use Cloudflare for the website for https://beatscratch.io https://beatscratch.io. However, I want to have a TLS-secured gRPC server also available on the
by pseudocomposer 3y ago
Yes, I use Cloudflare for the website for https://beatscratch.io https://beatscratch.io. However, I want to have a TLS-secured gRPC server also available on the same domain, which means using Cert-Manager, which is definitely easier if your DNS provider also does your Kubernetes service. I've been hopeful that I can keep all the things behind a single ingress and ideally served from a single Rust binary, but I'd love to see folks submit better solutions :)
- ramesh31 3y ago>However, I want to have a TLS-secured gRPC server also available on the same domain Now this is getting into opinion, but I don't believe gRPC was ever intended to talk to browsers. And with TLS termination in the mix, are you really even saving anything versus just translating to HTTP(S) and Gzipping for the clients? A typical setup is Backend -> protobuff grpc -> GQL/Auth server -> HTTPS -> client With the backend and GQL server in a VPC, so no need for TLS.
- pseudocomposer 3y agoYeah, I’m just eliminating the GQL server as it’s a bit redundant :) I’d argue that for what I want to do (single ingress everything), gRPC’s various language-specific frameworks handle TLS better than most (obviously not all) HTTP frameworks. Most HTTP frameworks just expect you to put them unsecured behind a separate ingress to do the TLS. For instance, as we can see with my own deploy here, Tonic (the Rust gRPC server) has handled TLS much better than Rocket (the Rust HTTP server).