Multi-region setup with write and read clusters

I’m interested in using FoundationDB as a highly available event store. I plan on using the multi-region setup. I understand that the reads of a client can also go to the warm secondary region, not only the hot primary region. I am fine with having some time lag so that I would use the cache to avoid version checks.

We want to have a setup with Kubernetes clusters that are distributed worldwide - most of them as read-only clusters and some of them as write clusters.

Is there a setup of FoundationDB that would make it possible with multiple locations? So far I would say no (or not really), also looking at this old topic Best configuration for worldwide low latency with small databases