I also just finished a project with F5s, GTM, LTMs, Cisco ISE and Cloud Pod. Likewise, I am not an F5 expert.
However, the F5 specialists were able to configure directing load balancers to the specific site based on a VLAN (and therefore IP) of the thin client. So it is possible.
What was NOT possible, is to have the F5 direct to a specific site based on AD username and/or specific domain membership derived from Horizon View protocol stream. Apparently, this functionality was removed from F5 code in the last few code versions (we are using 14.1.0 Build 0.0.116).
As a result, what we ended up doing:
1. Thin Client logs into AD.
2. Cisco ISE puts Thin Client into a specific VLAN based on AD login.
3. Horizon View client initiates the connection to a unified namespace.
4. F5 directs connection to the correct site's Connection Servers based on the specific VLAN.
5. Cloud Pod proxies the connection to the correct site's virtual desktop (redundant failsafe, as F5 was not wrong in the first place).
This was quite complex, but educational.
Sincerely,
Yury Magalif