Antonio Salazar Cardozo

I don't know that we'll see a significant performance boost during peer resolution, but regardless this seems like a good idea. We should likely introduce this as an optional config...

Couple of quick tests here: - Agree on ticket-based approach. - Checking in with Matt, it seems in an ideal scenario we'd be able to form multiple groups off of...

Fwiw, I'm trying to solve the giant issues that keep-network/keep-core#491 represents first, then follow up by figuring out how to factor out the code generators, and finally how we can...

Annoying that we can't mark one as “we get it and we're fine with it”.

Probably straightforward to achieve an initial version of this with a redirect.

This… Isn't always a good idea. You're going to want these to be pretty performant if you want to run them on every push. Another approach is to require that...

> I'd prefer to not leave any manual steps in the process. At a high level: I also don't like manual steps. That said, I'm only worried about manual steps...

This feels like if the operator is not yet registered the client should exit immediately. Then if e.g. kube wants to retry, it can employ whatever backoff.

> I will just start forking Promethea's beacon docs and filling them with vague guesses over here in this repo at some point. This is probably not the right thing...

Anyone out there? :)