This message was deleted.
# harvester
a
This message was deleted.
p
seems fine here
Copy code
k -v=8 get vmi 2>&1 | grep "Response Status"
I0219 22:25:01.959673   22961 round_trippers.go:574] Response Status: 200 OK in 3 milliseconds
I0219 22:25:01.962819   22961 round_trippers.go:574] Response Status: 200 OK in 1 milliseconds
I0219 22:25:01.977698   22961 round_trippers.go:574] Response Status: 200 OK in 5 milliseconds
b
yeah I got multiple cluster and some of them seem just fine, while others are stuggling.
just every once in a while...
Copy code
$ kubectl -v=8 get nodes -A 2>&1 | grep "Response Status"
I0219 14:58:24.922264   92920 round_trippers.go:574] Response Status: 200 OK in 72 milliseconds
I0219 14:58:24.935182   92920 round_trippers.go:574] Response Status: 200 OK in 11 milliseconds
I0219 14:58:24.991073   92920 round_trippers.go:574] Response Status: 200 OK in 20 milliseconds

$ kubectl -v=8 get nodes -A 2>&1 | grep "Response Status"
I0219 14:58:26.063078   92940 round_trippers.go:574] Response Status: 200 OK in 334 milliseconds
I0219 14:58:26.091824   92940 round_trippers.go:574] Response Status: 200 OK in 11 milliseconds
I0219 14:58:28.570796   92940 round_trippers.go:574] Response Status: 200 OK in 1691 milliseconds

$ kubectl -v=8 get backups -A 2>&1 | grep "Response Status"
I0219 14:57:04.366407   92714 round_trippers.go:574] Response Status: 200 OK in 1115 milliseconds
I0219 14:57:04.377369   92714 round_trippers.go:574] Response Status: 200 OK in 9 milliseconds
I0219 14:57:07.254995   92714 round_trippers.go:574] Response Status: 200 OK in 140 milliseconds
and sometimes the time to complete still seems to jitter? Like maybe the output stream gets paused for a hot second.
like :
Copy code
time kubectl -v=8 get backups -A 2>&1 | grep "Response Status"
I0219 15:01:36.394153   93398 round_trippers.go:574] Response Status: 200 OK in 195 milliseconds
I0219 15:01:36.551206   93398 round_trippers.go:574] Response Status: 200 OK in 132 milliseconds
I0219 15:01:37.938043   93398 round_trippers.go:574] Response Status: 200 OK in 149 milliseconds

real	0m2.380s
user	0m0.221s
sys	0m0.078s