Corosync and Pacemaker with Jails. Is it worth the effort?

Hello,

Are these cluster tools actually usable on FBSD and in Jails?

I got a 3 way PostgreSQL cluster with floating IPs to _mostly_ work across
3 Bastille-based jails but the whole process has been very painful, so I'm
wondering if this stuff is actually usable on FBSD or am I just wasting my
time, and this port is just a curiosity ?

I have noticed that several of the resource agents are very Linux oriented,
for example, requiring the ip command, and some of the very basic
clustering logic seem to depend on things like systemd.

So far I have discovered that you have to use VNET jail and I have had to
add:

allow.mlock = 1;
sysvmsg = new;
sysvsem = new;
sysvshm = new;

As well as this to corosync:
system {
       qb_ipc_type: shm
       sched_rr: no
       stonith-enabled: false
}

Not sure if there are other things I haven't noticed because even though I
finally got the cluster to run, the promotion and demotion seems very
unstable still.

Also, I cannot get rid of these warnings in every command:
WARNING: could not get the pacemaker version, bad installation?
WARNING: list index out of range

I am happy to continue the calvary if it's worthwhile and there are other
people using and/or interested in this, but the lack of information seems
to suggest that maybe this is just a waste of time, and these tools are
nowhere near a usable state without heavy lifting.

If the latter is the case, are there any other stable HA/Clustering
solutions that are mature for FBSD+Jails, and that include resource
managers such as databases (namely Pg and MariaDB) and floating IPs ?

This is the environment:
FreeBSD 14.0-RELEASE
Bastille: 0.10.20231125
Pacemaker 2.1.6
Corosync 3.1.7

Many thanks in advance, for any pointers or comments.

-- 
Alex