Ensure a new application that uses WebSockets and non‑distributed HTTP sessions will run correctly on Google Cloud.

The core challenge is maintaining WebSocket connections and non-distributed HTTP sessions across multiple instances. This requires a load balancer that supports WebSockets and sticky sessions (session affinity) to ensure a client consistently connects to the same backend instance. Convening cloud operations and the engineer is crucial to select the appropriate load balancer (e.g., Google Cloud Load Balancing with appropriate configuration) and confirm session affinity is correctly implemented. Converting WebSocket code to HTTP streaming is a significant application rewrite and might not be necessary if the load balancer can handle WebSockets. Reviewing encryption is important but doesn't address the core architectural challenge of session persistence. Redesigning the app for distributed sessions and removing WebSockets is also a major rewrite, potentially unnecessary, and doesn't directly solve the immediate problem of running the existing application.