-
Notifications
You must be signed in to change notification settings - Fork 20
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
Ability to configure service name #178
Comments
Can you explain more on this? We can add a field but I think a better solution is to actually understand how this specifically helps with migrations. Thanks. |
Thank you for your swift response and eagerness to help out.
Certain applications like Argo CD predefine an existing service name to use. This can be customized but using an existing name could help a migration. Also certain ingress controllers require a service name for a route. Rather than changing the existing name before a migration is complete a user could use an existing service name. |
It would be awesome if we could define the name of the service. Currently the service name is created statically by the name defined in the
Dragonfly
CR. Being able to customize the service name could be very helpful and speed up a migration of an existing Redis service.If accepted it would make sense to add it to the
serviceSpec
field.serviceSpec:
name: dragonfly-us-west-1
The text was updated successfully, but these errors were encountered: