Make --group mandatory #80
Comments
I think adding a required parameter reduces a bit of the magic that a |
Why not just use separate namespaces? Related: kubernetes/kubernetes#1698 |
We do offer namespace parameterization. However, we also want to allow for multiple instances of a chart (Redis) to live in the same namespace. The |
I am not totally convinced that we need to make I'd rather develop more of a use case than rush to implement this as described here. |
I'm supportive of adding some automatic label management to Kubernetes. |
The future of Helm is at kubernetes/helm. Helm Classic is in maintenance mode, so I'm closing this enhancement request. |
We need to make sure folks who deploy more than one instance of a helm chart into a single namespace don't end up getting very confusing results.
For example, if I have two instances of
redis-standalone
in thedefault
namespace and I use a simple label selector ofprovider=redis
my application will be automatically load balanced between all redis instances.We should probably make
group=...
parameter required.The text was updated successfully, but these errors were encountered: