Google HTTP(S) Load Balancing inherently supports the WebSocket protocol when HTTP or HTTPS (excluding HTTP/2) is used as the backend protocol. Therefore, the optimal approach is to engage with the cloud enablement team to explore load balancer options. There's no necessity to overhaul the application or switch to HTTP streaming, given Google HTTP(S) Load Balancing's WebSocket compatibility. While evaluating encryption requirements is beneficial, it's unrelated to WebSocket functionality.

Reference: Google Cloud Load Balancing Documentation