I do not see an option to enable F5 XC TCP connection multiplexing like the F5 OneConnect profile for HTTP 1.1 connections to the backend origin pool.
As XC uses envoy at the moment I suspect this article describes the option https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/connection_pooling
I see that feature called " connection reuse / connection pooling setting " can be disabled or enabled under the origin pool https://my.f5.com/manage/s/article/K000151090 Only thing F5 did not mention if for HTTP LB it is based on HTTP connections as one connect for F5 BIG-IP works differently https://my.f5.com/manage/s/article/K7208
You won't be notified about changes to this idea.
As XC uses envoy at the moment I suspect this article describes the option https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/connection_pooling
I see that feature called " connection reuse / connection pooling setting " can be disabled or enabled under the origin pool https://my.f5.com/manage/s/article/K000151090 Only thing F5 did not mention if for HTTP LB it is based on HTTP connections as one connect for F5 BIG-IP works differently https://my.f5.com/manage/s/article/K7208