As you know, when terminating a WebSocket connection due to releases CloudFlare now signals this action to both client and origin server by sending the 1001 status code (aka "going away", see section 7.4.1 of RFC 6455), so both sides are aware that the WebSocket termination is only a transient event, and that they can expect to immediately re-establish a connection again on retry.
We're working on additional refinements to the release process to minimize disruptions.
A colleague just published more details here https://blog.cloudflare.com/cloudflare-traffic-manager-the-d...