search

grafana / helm-charts

Apache License 2.0
1.65k stars 2.27k forks source link

[loki-distributed] Unable to disable some components #2746

Open verejoel opened 1 year ago

verejoel commented 1 year ago

We need to provision a dedicated read path for our ruler component. This means we only need queriers, query schedulers, and query frontends, without ingesters or distributors.

As it stands, we can re-use the loki-distributed helm chart, but only by setting ingester and distributor replicas to 0.

It would be good if every component had an enabled flag, do that as a user I can choose whether or not a component is deployed or not - regardless of whether that standalone deployment would "work" or not (heck, if the user just wants to deploy an index gateway in isolation, I think they should be able to).

peterballay commented 1 year ago

I agree this would be really beneficial. Only way is setting up replicas to 0, but it leaves orphaned resources or deployments with 0 replicas. I'm trying to achieve this with umbrella helm chart by using helm hooks and deleting resources I don't need.

vasekboch commented 10 months ago

I'm currently deploying a multicluster setup and I want to deploy the read and write paths separately. Some clusters needs only write components, and I have read components in separate cluster, dedicated for monitoring, with realtime uplinks to the write components. I have multiple orphnaed services, that I dont need.

I think that this chart should be highly customizable because its for people that need the distributed setup.