From 2f7486b70931648dccd0e6a5cbd97ae12fe86726 Mon Sep 17 00:00:00 2001 From: Tyler Brewer Date: Thu, 12 Oct 2023 12:02:46 -0400 Subject: [PATCH] explicitly state TLS termination location (#10516) --- docs/examples/grpc/README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/examples/grpc/README.md b/docs/examples/grpc/README.md index 508b23fb8..f6bd96e20 100644 --- a/docs/examples/grpc/README.md +++ b/docs/examples/grpc/README.md @@ -9,6 +9,7 @@ This example demonstrates how to route traffic to a gRPC service through the Ing 3. You have the ingress-nginx-controller installed as per docs. 4. You have a backend application running a gRPC server listening for TCP traffic. If you want, you can use as an example. 5. You're also responsible for provisioning an SSL certificate for the ingress. So you need to have a valid SSL certificate, deployed as a Kubernetes secret of type `tls`, in the same namespace as the gRPC application. + - Note: To use gRPC with ingress-nginx, TLS _must_ be terminated by the ingress or gRPC server (using the `backend-protocol: "GRPCS"` annotation described below). ### Step 1: Create a Kubernetes `Deployment` for gRPC app