planetscale / planetscale/vitess-operator
FEATURE: VTTablet naming
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 102
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 15
Description
Hi, is there some option to define custom naming of vttablet pods?
VTTablet pods are named like:
clusterName-vttablet-cellName-Tablet_UID-randomString
I would like to include keyspace-shard into naming instead having them on labels...
clusterName-vttablet-cellName-Keyspace-Shard-Tablet_uid-random string
Or if this gets too long for naming it like:
vttablet-Keyspace-Shard-TabletUID-randomString
cell in labels, clusterName in labels...
Or adjust values file to have an option for custom naming pods of vttablets and other components...
Looking at the pods list of vttablets i have no idea which one is for the specific keyspace/shard, until i read labels of the pod...
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 tracing how VTTablet pod names are currently assembled and how the values file configures pod settings. Compare the proposed naming alternatives with Kubernetes naming limits and existing labels, then define which configurable naming behavior and label preservation would count as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100