As you can see the watch function both takes 60s to access the name (and this is consistent every time) and only runs once, though it does take another 60s after the Took: 60 line is outputted for the Loop done line to be output.
This occurs both against a GKE cluster running 1.23 and a local k3s cluster running 1.25 using both the kubeconfig connection and a bearer token connection. It's also not just pods affected but other resources seem affected too.
Hi!
I'm hoping to write an operator in laravel but I'm finding that the watch method isn't working as expected.
Taking the following quick test command:
I get the following output:
As you can see the watch function both takes 60s to access the name (and this is consistent every time) and only runs once, though it does take another 60s after the Took: 60 line is outputted for the Loop done line to be output.
This occurs both against a GKE cluster running 1.23 and a local k3s cluster running 1.25 using both the kubeconfig connection and a bearer token connection. It's also not just pods affected but other resources seem affected too.