https://github.com/salrashid123/gcegrpc

gRPC client/server for Google Cloud (GKE, GCE, Istio, Traffic Director, grpc-web)
https://github.com/salrashid123/gcegrpc

envoyproxy gke google-cloud-platform grpc grpc-loadbalancing load-balancer traffic-director xds-server

Last synced: 7 days ago
JSON representation

gRPC client/server for Google Cloud (GKE, GCE, Istio, Traffic Director, grpc-web)

• Host: GitHub
• URL: https://github.com/salrashid123/gcegrpc
• Owner: salrashid123
• License: apache-2.0
• Created: 2015-08-30T03:07:14.000Z (over 9 years ago)
• Default Branch: master
• Last Pushed: 2024-11-25T12:00:08.000Z (about 2 months ago)
• Last Synced: 2025-01-09T03:32:58.116Z (14 days ago)
• Topics: envoyproxy, gke, google-cloud-platform, grpc, grpc-loadbalancing, load-balancer, traffic-director, xds-server
• Language: Go
• Homepage:
• Size: 1.24 MB
• Stars: 83
• Watchers: 6
• Forks: 22
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        

# gRPC on GKE and Istio

Samples for running gRPC on GKE, Istio, Gateway, Ingress, GCE VMs and Traffic Director:

## gRPC Loadbalancing on GKE with L7 Ingress

`client_grpc_app  (via gRPC wire protocol) --> ingress --> (grpc Service on GKE)`

- Folder: [gke_ingress_lb/](gke_ingress_lb/)

## gRPC Loadbalancing on GKE Gateway

`client_grpc_app  (via gRPC wire protocol) --> Gateway --> (grpc Service on GKE)`

- Folder: [gke_gateway/](gke_gateway/)

## gRPC Loadbalancing on GKE with TrafficDirector (xds loadbalancing)

`client_grpc_app  (acquire gRPC lookaside loadbalancing/XDS) --> GKE pod NEG address`

- Folder: [gke_td_xds/](gke_td_xds/)

## gRPC-web via Ingress

 Javascript clients:  

     

`client(browser) (via grpc-web protocol) --> Ingress --> (grpc Service on GKE)`

 - [grpc_web_with_gke](https://github.com/salrashid123/grpc_web_with_gke)

## gRPC for GKE internal Service->Service

- Folder [gke_svc_lb/](gke_svc_lb/)

      

`client (pod running in GKE) --> k8s Service --> (gRPC endpoint in same GKE cluster)`

## gRPC w/ Managed Instance Group with Container Optimized OS

- Folder [gce](gce/)

`client_grpc_app --> L7LB --> ManagedInstanceGroup`

## Istio gRPC Loadbalancing with GCP Internal LoadBalancer (ILB)

- folder `istio/`

`client_grpc_app (on GCEVM) --> (GCP ILB) --> Istio --> Service`

`client_grpc_app (external) --> (GCP ExternalLB) --> Istio --> Service`

Also see:

- [Summary of Cloud load balancers](https://cloud.google.com/load-balancing/docs/choosing-load-balancer#summary_of_cloud_load_balancers)

- [GCP LoadBalancing Overview](https://cloud.google.com/load-balancing/docs/load-balancing-overview#internal_tcpudp_load_balancing)

---

## Source and Dockerfile

You can find the source here:

- Client and Server: [app/grpc_backend/](app/grpc_backend)

And the various docker images on dockerhub

- `docker.io/salrashid123/grpc_backend`

To run the gRPC server locally to see message replay:

- Server:

    `docker run  -p 50051:50051 -t salrashid123/grpc_backend ./grpc_server -grpcport 0.0.0.0:50051`

- Client:

    `docker run --net=host --add-host grpc.domain.com:127.0.0.1 -t salrashid123/grpc_backend /grpc_client --host grpc.domain.com:50051`  

What client app makes ONE connection out to the Server and then proceeds to send 10 RPC calls over that conn.  For each call, the server

will echo back the hostname of the server/pod that handled that request.  In the example here locally, it will be all from one host.

## References

 - [https://grpc.io/blog/loadbalancing](https://grpc.io/blog/loadbalancing)

 - [gRPC Loadbalancing on Kubernetes (Kubecon Europe 2018)](https://www.youtube.com/watch?v=F2znfxn_5Hg)

 - [gRPC-web "helloworld"](https://github.com/salrashid123/gcegrpc/tree/master/grpc-web)

 - [gRPC with curl](https://github.com/salrashid123/grpc_curl)