Hi @brunolune
Were you able to get this running as a high availability cluster?
I won’t spend too much time explaining HA (figured you’d know if you’re trying to run in k8s) but want to clarify what we’re want out of this:
Availability & Sync: Any ceramic node data is available on any other node so if one node fails, the same data is available on the other node. Right now we can run multiple ceramic nodes but they each have their own data and they do not sync across each other.
We also want to snapshot the storage backend (not the nodes); In case all nodes fail (i.e.: invoking disaster recovery procedures). Have you sorted this out in k8s as well?
Would really appreciate 
if you can comment on any of this? BTW, I have a post about my ask (except we do not want to do this in k8s): Setting up HA Ceramic cluster plus node snapshots
Cheers,
Fadi