fix(kubernetes): recover compute driver watches (#2842)

Signed-off-by: Jesse Jaggars <jjaggars@redhat.com>

Author: jhjaggars

crates/openshell-driver-kubernetes/Cargo.toml

@@ -45,6 +45,7 @@ bytes = { workspace = true }
 http = { workspace = true }
 http-body-util = { workspace = true }
 temp-env = "0.3"
+tokio = { workspace = true, features = ["test-util"] }
 toml = { workspace = true }
 tower = { workspace = true }
 

crates/openshell-driver-kubernetes/README.md

@@ -60,7 +60,9 @@ state and platform events into the shared compute-driver protobuf surface used
 by the gateway.
 
 Kubernetes API calls use explicit timeouts so gRPC handlers do not block
-indefinitely when the API server is slow or unavailable.
+indefinitely when the API server is slow or unavailable. Resource and Event
+watches recover in place with API-friendly backoff after transient watcher
+errors, avoiding a gateway-side watch restart and its associated watch gap.
 
 ## Workspace Persistence