fix(kyverno): raise admission-controller resources + dev replicas 2 to stop fail-closed crashloop/502s

Admission controller was crashlooping (9 restarts/4h, exit 255, NOT OOM:
live usage ~65Mi/384Mi limit, 7m cpu). Root cause: chart-default 100m CPU
request starved the process under node contention, so client-go calls hit
context-deadline-exceeded, leader-election lease renewal timed out, leadership
was lost and the webhook server closed. Raise the CPU request to 250m (no CPU
limit, to avoid CFS throttling) with modest memory headroom (256Mi/512Mi), and
raise dev admission replicas 1->2 so a single fail-closed pod restart no longer
502s cluster-wide admission-gated writes.

Co-Authored-By: Claude Opus 4.8 <[email protected]>

platform/kyverno/admission/helmrelease.yaml

@@ -49,6 +49,19 @@ spec:
     # restart cannot open an enforcement gap; dev drops to 1 to save RAM during bootstrap.
     admissionController:
       replicas: ${KYVERNO_ADMISSION_REPLICAS}
+      # Resources — chart default (limits.memory 384Mi / requests.cpu 100m,memory 128Mi) starves this
+      # latency-sensitive, fail-closed webhook: under node CPU contention the 100m request gave too few
+      # CFS shares, so client-go calls hit "context deadline exceeded" → leader-election lease renewal
+      # timed out → "leadership lost, stopped leading" → server closed (exit 255, NOT OOM: live usage
+      # was ~65Mi/7m). Raise the CPU REQUEST for scheduling headroom and keep NO CPU limit (a limit would
+      # reintroduce throttling and make lease-renewal timeouts worse). Memory bumped for headroom only.
+      container:
+        resources:
+          requests:
+            cpu: 250m
+            memory: 256Mi
+          limits:
+            memory: 512Mi
     backgroundController:
       enabled: true               # needed for generate (default-deny baseline) + sync
     reportsController: