Investigate k8s javascript client watcher timeouts
Description
This issue is based on this comments thread. We should investigate, why watch connections in the k8s javascript-client are timing out after approximately 5m.
Definition of done
We have a reason of why this is happening documented here, and in the javascript-client. If it is a configuration issue, we should also note how to change/avoid it.
Some clues for the investigation
My best guess so far that it's a direct consequence of browsers timing out the HTTP calls (and the current implementation of the java-script client works with https calls instead of websocket connection). For example chrome timeout matches what we experience. But that has to be properly verified.
as per @timofurrer comment the k8s API itself doesn't have any imposed timeouts.
Edited by Andrei Zubov