Set up a Load Balancer for the PMC Environment
The load balancer must be installed after you have installed PMC, not before.
You need to install and configure a load balancer to balance the load across the cluster before you continue. You can choose which load balancer you use to do this. There are four rules that need to be created:
Incoming traffic from your endpoints on port 443 needs to be balanced across all PMC cluster nodes.
Incoming traffic from trusted admin IPs and the PMC cluster on port 8443 needs to be balanced across all PMC cluster nodes.
Sticky sessions, or session affinity, is required for port 8443.
Incoming traffic from trusted admin IPs on port 9443 should not be balanced across the PMC cluster. It must be directed at the node where the PMC portal is deployed.
Incoming traffic from trusted admin IPs on 19080 (Service Fabric Explorer) and 19000 (Service Fabric interface using PowerShell) needs to be balanced across your PMC cluster nodes.
You need to check the timeout settings on the load balancer to ensure that they are set to five minutes, as this is the timeout setting applied to the Reporting Gateway service for PMC. If you do not adjust the timeout settings in your load balancer, where present, reports in PMC may time out unexpectedly.
Some load balancers may require your SSL certificate to be uploaded or installed. See the specific documentation for your load balancer for these requirements. If your load balancer requires the SSL certificate, you must not terminate SSL at the load balancer.