When loading data for the first time with useFleetK8sWatchResource and it is not already cached, like on page reload, it takes several seconds for the data to appear. There appears to be a delay before the watch WebSocket is opened. We need to investigate the timing of the initial GET and subsequent watch call to see where the delay is originating and if it can be improved.