I'm like 90% sure rook-ceph dualStack and ipFamily IPv6 flags are bugged out. They don't enable ms_bind_ipv6 causing the mons to fail out leading to a single mon-a which ofc doesn't spin up the osds due to no quorum
or maybe not... Using flags over config I think

mmm, I have no idea. I guess I'm just have to trust that with ROOK_POD_IP set to v6 and ms-bind-ipv6 flags it's actually using v6. I did ask on the github discussions page so we'll see.

Also it's completely possible all my issues getting mons started are stemming from "uncleaned" drives as sometimes it works and sometimes it doesn't. 🫠

Travis confirmed that the flags have higher preference so my cluster is running v6 :D

https://github.com/rook/rook/discussions/17214#discussioncomment-16215010

Is IPv6 bound even with ceph config ms_bind_ipv6 false? · rook rook · Discussion #17214

Is IPv6 the binding address even tho ceph config shows ms_bind_ipv6 as false? kubectl -n rook-ceph exec -it $(kubectl -n rook-ceph get pod -l "app=rook-ceph-tools" -o jsonpath='{.items[*].metadata....

GitHub