diff --git a/apps/selenium/selenium-grid.yaml b/apps/selenium/selenium-grid.yaml index 7f207c0..62d84a1 100644 --- a/apps/selenium/selenium-grid.yaml +++ b/apps/selenium/selenium-grid.yaml @@ -132,13 +132,18 @@ spec: initialDelaySeconds: 10 periodSeconds: 5 timeoutSeconds: 5 + # Hub baseline working set ~766Mi on 2026-05-25 (75% of prior 1Gi + # limit). Bump to 1.5Gi / 1Gi to keep ~50% headroom; matches the + # stampede-buffer pattern documented for multus + # (feedback_k8s_cni_multus_sizing). CPU left alone — observed 54m + # against a 500m limit, no contention. resources: limits: cpu: 500m - memory: 1Gi + memory: 1536Mi requests: cpu: 250m - memory: 512Mi + memory: 1Gi --- apiVersion: apps/v1 kind: Deployment @@ -198,13 +203,18 @@ spec: port: 5555 initialDelaySeconds: 15 periodSeconds: 5 + # Chromium-based browser node. Bumped from 1Gi -> 2Gi (req 512Mi + # -> 1Gi) on 2026-05-25 — Edge had 51 OOMKills in 5d on the + # original 1Gi cap (~1 OOM every 2.4h), and Chrome at maxSessions=2 + # was running 684Mi idle on the same cap. Matches the Firefox node's + # tested-stable 2Gi limit. CPU unchanged. resources: limits: cpu: '1' - memory: 1Gi + memory: 2Gi requests: cpu: 500m - memory: 512Mi + memory: 1Gi volumeMounts: - mountPath: /dev/shm name: dshm @@ -378,13 +388,18 @@ spec: port: 5555 initialDelaySeconds: 15 periodSeconds: 5 + # Chromium-based browser node. Bumped from 1Gi -> 2Gi (req 512Mi + # -> 1Gi) on 2026-05-25 — Edge had 51 OOMKills in 5d on the + # original 1Gi cap (~1 OOM every 2.4h), and Chrome at maxSessions=2 + # was running 684Mi idle on the same cap. Matches the Firefox node's + # tested-stable 2Gi limit. CPU unchanged. resources: limits: cpu: '1' - memory: 1Gi + memory: 2Gi requests: cpu: 500m - memory: 512Mi + memory: 1Gi volumeMounts: - mountPath: /dev/shm name: dshm