Confusing info box in the Operator documentation
jerrinot opened this issue · comments
@jerrinot the reason for this is that readyMembers
are listening for the MembershipStateChanged
s which are fire-and-forget events. Thus we do not recommend to thread it a reliable source of truth. But I agree that this can be described more thoroughly
How does this affect users?
In what circumstances would this value be inaccurate?
What more accurate ways do we offer to check how many active members are in the cluster?
@JakeSCahill I don't think there is a precise scenario when this value is inaccurate. The more accurate data will be provided in the future with the implementation of advanced cluster status
So the potential for a user to see an inaccurate value there is negligible?
Maybe the best course of action is to remove the warning.