-
Notifications
You must be signed in to change notification settings - Fork 93
Description
Is your feature request related to a problem? Please describe.
Attempting to deploy two DSS instances to a single AWS VPC is successful at the terraform deployment level, but fails quietly when attempting to deploy AWS LoadBalancers through a Kubernetes LoadBalancer Service object.
These LoadBalancer Services should be configurable so that a name clash is avoidable, even if they aren't set by default.
Describe the solution you'd like
I've provided a PR with a sample solution: #1188
The clashing components cockroachdb external node service and dss gateway external service should have at least partially configurable names so that a deploying user can alter the names after seeing the clash OR they should be unique to begin with.
Describe alternatives you've considered
An alternative is a user manually altering the resources locally and then performing their deployment. But it requires a deeper understanding of the helm chart, and implies that it ought not be allowed, but can be manually worked around.