Patrick Oyarzun

I agree with Joe about adding to the +gen comments. I think those should exist to override the default 'magic' behavior. Also, I'd appreciate the ability to generate all methods...

I've written a demo typewriter for pipelines [here](github.com/Logiraptor/streams). It's only about an hour's work so there are definitely rough spots. The biggest challenge with this is early termination. I've had...

Documenting the migration strategy for existing Helm users: ## Preparation ### Step 1 - [ ] Set the zone for all ingesters to `zone-default` - [ ] Deploy 3 new...

I wonder if we should add a step for simplicity where we enable `ingester.ring.unregister-on-shutdown` and `blocks-storage.tsdb.flush-blocks-on-shutdown` for the zone-default ingesters. Would this let us skip the complicated scale-down process in...

Proposed configuration for the migration so we have something to think about: ```yaml migration: multizone: step: 1 # This value would be incremented from 1-8 throughout the migration ``` Internally,...

@09jvilla @krajorama @dimitarvdimitrov @ortuman Thoughts on the proposal here ^. I believe this is similar to what @krajorama has proposed in the past.

Current state: @ryan-dyer-sp is going to move the PR from the helm-charts repo over here next week and we'll go from there.

@pracucci thanks! > The problem is that when you'll revert the change back (which requires an ingesters rollout), it will unregister ingesters and flush blocks for multi-zone ingesters too. I...

Thanks for filing this issue @ama-source. I know of a few issues right now: 1. nginx is wholesale replaced with the GEM gateway, this means any ingress you have using...

What if we re-use the existing `gateway` section for the new unified reverse proxy? Is it possible then to make this a seamless upgrade for paying customers with a migration...