Allow custom vtgate/vtctld Service names
enisoc opened this issue · comments
Currently, the vtgate Service name has a unique, deterministic hash suffix. This was part of a strategy to avoid collisions in the multi-tenant environment for which our operator was initially designed. For those running the operator in their own, controlled environments, the hash suffix makes it unnecessarily difficult to configure apps to connect to Vitess.
We should make the hash suffix optional for at least the main vtgate/vtctld Services, and possibly also the per-cell vtgate Services. Ideally we would also make the suffix disabled by default, but unfortunately that would be a backwards-incompatible change for those of us already running the operator in production.
To avoid over-constraining the user's choice, we could support this by adding an optional field to override the default Service name to a custom value.
Defining the k8s service name in the CR yaml and keeping the deterministic hash suffix as the default sounds the most intuitive to me.
Hey there, any movement on this?
Thanks!
We haven't worked on this yet. Unfortunately I'm busy with other projects at the moment, but if anyone wants to take this on I can offer some pointers.
Any updates...?