Lucas Servén Marín

Great suggestion, @roidelapluie. The current implementation in master is simply broken whenever you write the second time, even ignoring race conditions, so what @allenmqcymp is proposing is a net-improvement IMO....

Hi @chfxr I did some digging and found the cause of this SNAT. Kilo masquerades packets when they come from peers [0] and go to IPs that Kilo doesn't know...

> A --service-cidr flag would be sufficient to use this feature. Excellent I'll put something together.

Let's be careful with our words here: I don't think there is anything"misleading" in the text, as that implies negative intent. "Our plan is for Thanos Receive to create a...

@tend2infinity could you rebase on main? Docs are building correctly there and there were done changes recently

What do you mean exactly by: > What you expected to happen: Thanos-receive is able to upload old data to S3. Thanos receive is already able to upload old data...

aha, ok so you mean something like: > What you expected to happen: Thanos-receive is able to continue ingesting data even after closing and uploading a block without seeing out...

@rushins thanks for reporting this. Can you provide us with some more information on your cluster so we can understand how to reproduce the issue? How many nodes are in...

@bodgit bare-metal installations of tectonic are *not* expected to run ingress on port 32000. Bare-metal installs should have a hostPort [0] based ingress controller listening directly on port 443 [1]....

@bodgit I see. Your situation is a little different from @dmgaraway's. In your case, the tfvars posted in the google groups thread indicate that you deployed Tectonic onto vmware, which...