From 05993e8a132b695a5ac7c648c9af0a6c499bafc1 Mon Sep 17 00:00:00 2001 From: Shreyans Sheth Date: Wed, 23 Jan 2019 17:02:16 +0530 Subject: [PATCH] Correcting links for gRPC Fortune Teller app The link was erroneous, corrected the same. --- docs/examples/grpc/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/examples/grpc/README.md b/docs/examples/grpc/README.md index 0416f5e07f..06dcb5664e 100644 --- a/docs/examples/grpc/README.md +++ b/docs/examples/grpc/README.md @@ -17,7 +17,7 @@ nginx controller. for grpc support. 4. You have a backend application running a gRPC server and listening for TCP traffic. If you prefer, you can use the - [fortune-teller](https://github.com/kubernetes/ingress-nginx/images/grpc-fortune-teller) + [fortune-teller](https://github.com/kubernetes/ingress-nginx/tree/master/images/grpc-fortune-teller) application provided here as an example. ### Step 1: kubernetes `Deployment` @@ -30,7 +30,7 @@ This is a standard kubernetes deployment object. It is running a grpc service listening on port `50051`. The sample application -[fortune-teller-app](https://github.com/kubernetes/ingress-nginx/images/grpc-fortune-teller) +[fortune-teller-app](https://github.com/kubernetes/ingress-nginx/tree/master/images/grpc-fortune-teller) is a grpc server implemented in go. Here's the stripped-down implementation: ```go