In our compiler installation docs, we mention multi-region/multi-data-center setups in a few subsections. If you follow these instructions to a tee, you'll end up with all your agent nodes connecting to a single compiler/load balancer (bar the install script) instead of each region's compiler/load balancer. This defeats the purpose of even setting up compilers local to each data-center.
Current text :
Under "Load balancing for geodiverse locations":
If you have load balancers in multiple data centers, set the pe_repo::compile_master_pool_address in Hiera at the point of locational demarcation. With multiple data locations, specify this value at the lowest point in your hierarchy that still accurately provides appropriate values for each location. For example[...]
Under "Configure compilers":
Important: If you have load balancers in multiple data centers, you must configure compile_master_pool_address using Hiera, instead of using configuration data in the console, as described in this step. Using either of these methods updates the agent install script URL displayed in the console.
In the "Load balancing for geodiverse locations" section, we should include instructions on configuring the puppet_enterprise::profile::agent class's manage_puppet_conf, pcp_broker_list, master_uris, server_list parameters per-region in hieradata.
In the first "Important" notice box under "Configure compilers", mention the above parameters in addition to compile_master_pool_address, and recommend skipping the entire "Configure compilers" section's steps.
In multi-region scenarios, the steps we provide will configure agent nodes to connect to a single load balancer/compiler (bar grabbing the install script). This needs to be changed, else we're negating the purpose of multi-region compilers/load balancers.