Alvin Lin

@pracucci and @pstibrany for this issue, do you think it would be an improvement if we change the compactor not to halt the whole compacting process when a level1 block...

+1 binding.

With 4/4 +1s, I declare the governance update is effective as of now :)

@jakubgs so if you use the `-.consul.acl-token` command line argument to Cortex everything works, but if you configure the same in YAML everything works? If possible would you be able...

My opinion is dropping everything is safer option because it will be very obvious to the receiver that something is wrong. For example, in the case where message body is...

@simonpasquier would you be able to kindly restart the failed workflow? It failed due to transient issue it seems like: ``` error pulling image configuration: Get https://quayio-production-s3.s3.amazonaws.com/sha256/57/57b64f8a7d6913f7c594d442d7d51bd1814d32b8717b75ef7d038c4f1d085015?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAI5LUAQGPZRPNKSJA%2F20220214%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220214T090947Z&X-Amz-Expires=600&X-Amz-SignedHeaders=host&X-Amz-Signature=0e9aa0b2baf73e04e98ae98851876611eb2570a6bc5933bac380d624315dbad1: net/http: TLS handshake...

I think migrating to an actively maintained lib is always a good idea. I am not sure about the migration effort though since I haven't been working with Go ecosystem...

@GiedriusS based on https://github.com/thanos-io/thanos/pull/5504 it looks like Thanos moved away from depending on Cortex; in this case, this issue is not blocking your work on https://github.com/thanos-io/thanos/pull/5421 anymore right?

> Reopening. Need clarification on the reported. I just learned that the document in question was written assuming `Deployment`. That's why the doc talks about `maxUnavailable` and `maxSurge` for ingesters.

@zspeaks can you also share an example how the actual log looks like?