planetscale / planetscale/vitess-operator
[Feature Request] Expose vtgate service by nodeport or load balancer
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 102
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 15
Description
Generally there are 2 ways (nodeport or load balancer) to expose vtgate service to outside of k8s cluster.
Currently the Vitess cluster CRD provides the ServiceOverrides structure for us to tweak some properties of vtgate service. But this structure doesn't provide the capability for tweaking nodeport or load balancer settings.
So the only way for us to expose the vtgate service to outside k8s cluster is to add another layer of ingress gateway over the vtgate. This will cost extra overheads on the mysql connection roundtrip.
So please make it possible to expose vtgate (even other vitess related service) by nodeport or load balancer through vitess cluster CRD.
Related slack thread: https://vitess.slack.com/archives/C0PQY0PTK/p1638621405356000
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
Start by reading the Vitess cluster CRD and its ServiceOverrides structure, then inspect how the vtgate service is defined. Determine how NodePort and load balancer settings should be represented for vtgate. Done means vtgate can be exposed outside the Kubernetes cluster through the CRD without requiring an additional ingress gateway.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100