Just catching up this morning. Like @TomF , I was also tricked by isActiveFlowIndication() and will remove it from my previous post to avoid confusing others.
If you can’t leverage kubernetes stateful sets, which feels like the cleanest solution to me, then I like @TomF 's suggestion to maybe connect to all the Qs and stay connected to the first one that says you’re active + close the flows listening to the others. So sorry for the confusion!