Kind of. There is an ongoing discussion regarding HA and clustering fore Foreman over on the development forum.
Firstly, you can use a capsule server to manage and store content for each of your datacenters. This is so that you don’t have to transmit ISO images and deb/rpm packages over site-to-site VPNs or point-to-point connections, thus saving your time and bandwidth. These all roll up into a centralized foreman instance however.
You should be able to configure that behind a load balancer (F5, A10, nginx, corosync, etc), but to be truly redundant, you would also need to mirror your database layer. You could do this with MaxScale from MariaDB, ScaleArc or MySQL Proxy, but you will still run into issues with your Smart Proxies. Some of them can’t handle a failover during operations, though some of them can. Those that can can be placed behind a load balancer, but for the remaining, you would have a single point of failure at each datacenter.
The real question though is if you need this level of redundancy and complexity for a system that manages patching and spins up and down VMs. The decision in my environment has been, things will operation normally with no customer impact if our foreman instance gets blown away. It will be some hard work to get it back online, but it doesn’t need to be redundant like that. We can continue to operate for a day or two without our patching depot and orchestration server.