There are no specifically supported or unsupported load balancers at this time. How to put a Unified Workspace server+relay or relay behind a load balancer is not much different than how you would put any other web server.
You will want to have your load balancer handle the redirect from port 80 to port 443, so that all communication is performed using ssl.
Verify load balancer persistence (sticky sessions) is configured. For example, when a user is sent to server1, they will stay with server1 until such time when server1 is unavailable. If you let them bounce between any Unified Workspace server after initial connection then many web applications (PROXY) will fail because you end up sending them to a server that is not ready to handle their connection. If you do not use Unified Workspace clustering service, you would have a similar situation where servers are not aware of other sessions and would be prompted for login again. Various types of persistence may exist on a load balancer the recommended is cookie persistence; however, this may vary based on options available.
If you are going to offload SSL, then this options need to be turned on the Unified Workspace relays (webAdmin -> Relay Admin) and the service needs to be restarted. Some load balancers have an option for an SSL Bridge which will then pass the data thru the load balancer untouched to the relay. You would still need to have SSL enabled on Unified Workspace relays. This option however prevents the real ip number from the user (x-forwarded-for) to be sent from the load balancer so you may have issues with all users looking like they came from the load balancer.
If you have any PROXY web applications that use alternate ports, you may have to also configure those to go through the load balancer. We've found that with some load balancers, they must be configured with a single service to handle all ports, versus have separate services for each port. Otherwise, the load balancer balances the ports separate and causes connection issues.
The Unified Workspace session is stored in a session cookie called CStoneSessionID, this cookie needs to be passed with each request to the relay.
For testing / debug purposes with Unified Workspace, it is important to have a way to test outside of the LB. It's possible some issues are simply a misconfiguration on the load balancer and not a Unified Workspace code or configuration issue.
If you have a new load balancer or have never configured your load balancer before, then it is best practice to test with a test Unified Workspace server or other less used web servers. If you need assistance setting a test Unified Workspace server, please contact support.
Make sure you are able to contact your vendor for support on your specific load balancer as Lenovo Software can only provide general configuration suggestions and not specific configurations for your model of load balancer.
Make sure your timeout for the load balancer is slightly greater than your timeout for Unified Workspace. The default timeout for a new installation of Unified Workspace is 60 mins, but is configurable in the Server Management Console.
If you are using HTML5 webRDP client you will need your load balancer to pass WebSockets. Depending on the load balancer, there may be an option to enable WebSocket support. If not, setting the Load Balancer to balance TCP versus HTTP may allow WebSockets to properly pass through.
For correct logging and PersonalRDP, you will want to add "X-Forwarded-For" header to request to pass the users IP address to Unified Workspace server(s).