-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature request] Allow for Service
name overrides
#405
Comments
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? |
Hi @walkamongus isn't the
|
This was also reported: Should be at CRD vitessclusters, define the serviceName for vtgate and vtctld. For vtgate service I believe that should be here, but there is no serviceName property At the moment, once there is no support for this in the helm chart, I've created my own templates: The same for vtadmin. Would be nice to have a way to expose 2 ingress: UI and api. Regarding ingress for vtagte/vtctld/vtadmin, maybe in vitessclusters CRD spec: ingress:
properties:
annotations:
additionalProperties:
type: string
type: object
className:
type: string
labels:
additionalProperties:
type: string
type: object
serviceName:
type: string
hostName:
type: string
tls:
items:
properties:
hosts:
items:
type: string
type: array
secretName:
type: string
type: object
type: array
type: object |
I ran into an issue exposing endpoints externally when trying to use an
Ingress
resource. If theVitessCluster
CRD allowed for overridingService
names viaserviceOverrides
then users would be able to set a predictable name forService
resources. That would allow users to inject anIngress
resource via Helm or Kustomize that references the correctService
name. Alternatively -- for more work (and likely more fragile implementation) -- the custom resource itself could be extended withIngress
support.The text was updated successfully, but these errors were encountered: