[Feature request] Allow for Service name overrides

[walkamongus]

I ran into an issue exposing endpoints externally when trying to use an Ingress resource. If the VitessCluster CRD allowed for overriding Service names via serviceOverrides then users would be able to set a predictable name for Service resources. That would allow users to inject an Ingress resource via Helm or Kustomize that references the correct Service name. Alternatively -- for more work (and likely more fragile implementation) -- the custom resource itself could be extended with Ingress support.

[oavril]

Hi !

I'm also interested in adding the ability to override the name and add labeling of services to create a helm including an ingress and a loadBalancer.

Unless you provide an official helm chart?

[frouioui]

Hi @walkamongus isn't the service field of the vtgate CRD sufficient for this?

vitess-operator/pkg/apis/planetscale/v2/vitesscell_types.go

Line 223 in 23decc9

Service *ServiceOverrides `json:"service,omitempty"`