[Feature Request] Expose vtgate service by nodeport or load balancer

[tokikanno]

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

[marf]

Hello, any news about this?

We want to avoid adding an extra layer of ingress gateway if possible.

[ajitspendse]

Another way to expose the service is to manually change the deployed service to type LoadBalancer or NodePort and (optionally) provide the IP or port to use. However, this also introduces a manual step that is best avoided. Support for different service types (LoadBalancer/NodePort) would be great addition.

[mattlord]

This would be a nice contribution from a person/party that really wants to use it.

[aagarwal-apexanalytix]

Opened #791 implementing this. Adds Type, LoadBalancerIP, and ExternalTrafficPolicy to the existing ServiceOverrides struct (so every Service the operator already overrides — gateway, vtctld, vtadmin, etcd-lockserver, vttablet headless — gets the new fields for free). Single commit, DCO-signed, with 4 new unit tests + regenerated CRDs.