Tchirana

here is a snip from 2 nodes starting in the same time: kubeip-f26p9 kubeip time="2023-12-06T14:20:15Z" level=debug msg="found 8 available addresses" kubeip-mr6kt kubeip time="2023-12-06T14:20:18Z" level=debug msg="found 8 available addresses" AND: kubeip-g9mxj...

It would be very useful for commamd like cluster info to get json output. Very usefull in scripting.

@alex-zaitsev @mandreasik I have the same issue in 25.3 op version. [Here](https://github.com/Altinity/clickhouse-operator/issues/1796) the issue. What is more critical is that during a upgrade of chk chi pods loose comms with...

Hello, just the normal stuff of replacing the image in the chk installation manifest. What is even more weird that we have several clickhouses in different clusters , all of...

@alex-zaitsev renamed the issue since you are correct with the PDB. That does take effect because operator sets up 1 pod per sts.

I really think it is a race condition because it makes no sense. On some clusters those chk pods behaved, on others they restarted chaotically, all at once, 2 at...

because of this we usually stop all that puts data in clickhouse, stop chi pods and after that do maint on chk, otherwise there is a very big risk in...

@spirkaa yeah. We fck-ed an entire cluster because of this and it was a nightmare to get databases back from read-only. We were gratefull we have dev environment :)