Initial spike in network traffic for kubectl delayed

[legomushroom]

Initial spike in traffic to a remote kube cluster using kubectl is delayed due to large number of concurrent requests made by the tool(~20 requests). This results in delay at the beginning of the session(~20 seconds) after which kubectl works as expected.

This might be caused by a large initial traffic, large number of initial requests or logic flaw in threading logic(we currently use max(cores count, 12) threads).

Logs: 2022-06-28_21-local-vpn-gateway_REJT3CLE.log

[legomushroom]

Fixed in v0.12.4 🚀