planetscale / planetscale/vitess-operator
[Feature request] Allow for `Service` name overrides
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 102
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 15
Description
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.
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 locating the VitessCluster CRD and the code that creates its Service resources. Then inspect how Helm or Kustomize could reference those Services for an Ingress. Done means a defined serviceOverrides behavior produces predictable Service names and supports the stated external Ingress use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100