gRPC Outside the Cluster - A Guide
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 221
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 1
Description
At the recent gRPCConf, we heard reports of the challenges of using gRPC resources outside of Kubernetes clusters. This post covers the various challenges a developer or SRE may face in successfully using gRPC outside of their cluster - HTTP2, ingress config and mapping, external load balancing, among others - and suggests solutions and deployment patterns to effectively utilize gRPC resources outside of Kubernetes clusters.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named, so start by reviewing the website's existing guide structure and any current gRPC or Kubernetes documentation. The work is done when a guide explains the external-cluster challenges named in the issue, including HTTP/2, ingress mapping, and external load balancing, with deployment patterns and suggested solutions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, kubernetes
- Domain
- documentation, networking
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100