John Spray

> I think we should only really expose what is necessary to start and obtain results from buildkite, probably only 22 and have the other ports only reachable from other...

>> Maybe we just remove that cidr_blocks from the 9092 ingress rule. > Will this affect our ability to run the ducktape runner from our laptops? Yes, if this was...

@graphcareful this is still assigned to you: are you working on closing the ports?

Sorry, those "Status endpoint unavailable" ones are my fault, I forgot to do this: https://github.com/redpanda-data/vtools/pull/910

This may or may not be related, but there's a big rework of the kgo-verifier wrapper services https://github.com/redpanda-data/redpanda/pull/6059 here that should make them more robust (stop running them captively on...

We currently have two extremes: - the controller raft group, which provides robust leadership election and replication of the persistent parts of the cluster state. This includes members_table, topics_table etc....

I haven't looked in to these, don't know if they make sense when running against real S3?

Checked if this was related to #5613 and no: this one is a storage assertion, that one is a segfault.

If I had to guess, my suspicion would be that this is something in the SI cache changes, tearing down readers uncleanly on eviction perhaps.

> Am I reading this right that two nodes failed, one with the segment_reader.cc:215 assert but then one with a future.hh:641 assert (in the seastar future internals)? Yes. I didn't...