Skip to content
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

Open
walkamongus opened this issue Apr 6, 2023 · 1 comment
Open

[Feature request] Allow for Service name overrides #405

walkamongus opened this issue Apr 6, 2023 · 1 comment

Comments

@walkamongus
Copy link

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
Copy link

oavril commented Aug 10, 2023

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants