XAMPPRocky

@markmandel We tried replicating it again, but couldn't. It's odd I could consistently replicate it over the weekend on multiple machines, monday comes around, and I couldn't replicate it. I'll...

I think the simplest solution is to remove the idle interval on the agent, I don't think it's turned out to be intuitive, and the connection stability has been more...

> Will next dig into why that is, but @XAMPPRocky if you have suggestions also happy to take them. I don't unfortunately, I can't replicate in prod, I think it...

What I've seen in the the logs is usually stuff attempting to connect before a service is ready and then getting stuck in that.

> (would also love some time to step through the agent + xds client/server code at some point to see if we can see something toghether. Sure, I'm bit a...

Well I closed that PR because nearly everything has been cherry-picked into main now or we've implemented better solutions than the hacks I added. Nothing in that PR really touched...

Thank you for your issue! That definitely seems like a bug, it's definitely not intentional or intuitive behaviour.

Thank you for your issue! We discussed this at our last community meeting, and the work to support this feature should be minimal. > game server in a K8S cluster...

> There is a secondary use case, but I would expect us to leverage Quilkin via xDS configuration control plane for that, where we would deal with the "watching" since...

I'm not sure I see the value of it being optional. Even if you're hosting in the same datacentre, understanding the latency between hops is important, as latency isn't only...