fix(network): raise overlay-test CPU limit and latency thresholds

The overlay-test pod's 10m CPU limit caused CFS throttling (88% of
scheduling periods), inflating HTTP probe latency from ~3ms to 300-500ms
on ARM/Pi nodes. This triggered false-positive NetworkDegraded alerts.

- Bump overlay-test CPU: 1m/10m -> 5m/100m (eliminates CFS throttling)
- Raise warning latency: 50ms -> 200ms (HTTP probing baseline on ARM)
- Raise critical latency: 200ms -> 500ms

Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>

Author: mattmattox

helm/node-doctor/templates/configmap.yaml

@@ -101,8 +101,8 @@ data:
             probePath: /healthz
             pingCount: 3
             pingTimeout: 5s
-            warningLatency: 50ms
-            criticalLatency: 200ms
+            warningLatency: 200ms
+            criticalLatency: 500ms
             failureThreshold: 3
             minReachablePeers: 80
           cniHealth:

helm/node-doctor/values.yaml

@@ -400,10 +400,10 @@ overlayTest:
   # Resource limits for overlay test pods
   resources:
     requests:
-      cpu: 1m
+      cpu: 5m
       memory: 8Mi
     limits:
-      cpu: 10m
+      cpu: 100m
       memory: 16Mi
 
   # Update strategy

pkg/monitors/network/cni.go

@@ -16,8 +16,8 @@ const (
 	// Default configuration values for CNI monitor
 	defaultCNIPingCount             = 3
 	defaultCNIPingTimeout           = 5 * time.Second
-	defaultCNIWarningLatency        = 50 * time.Millisecond
-	defaultCNICriticalLatency       = 200 * time.Millisecond
+	defaultCNIWarningLatency        = 200 * time.Millisecond
+	defaultCNICriticalLatency       = 500 * time.Millisecond
 	defaultCNIFailureThreshold      = 3
 	defaultCNIMinReachablePeers     = 80 // percentage
 	defaultCNIRefreshInterval       = 5 * time.Minute