selenium: migrate hub + 3 nodes into ArgoCD-managed manifests #25

bluejay · 2026-05-26T00:09:24Z

bluejay commented

2026-05-26 00:09:24 +00:00

No description provided.

bluejay added 1 commit 2026-05-26 00:09:25 +00:00

selenium: migrate hub + 3 nodes + service + ingressroute into ArgoCD 2f796a2ebd

Previously orphan kubectl-applied since the Selenium Grid was first set
up. The `infra-selenium` ArgoCD app existed but only managed
`network-policy.yaml` — the deployments themselves drifted whenever
anyone `kubectl set env`'d or `kubectl scale`'d.

This commit captures the live state (with the 2026-05-25 maxSessions
bump for chrome already baked in) as canonical git source. ArgoCD's
ServerSideApply syncPolicy + selfHeal will now keep the grid in lock
step with this file.

Resources captured:
  - Service selenium-hub (ClusterIP, internal traffic on 4444)
  - Service selenium-hub-external (LoadBalancer, MetalLB 10.0.56.208)
  - Deployment selenium-hub
  - Deployment selenium-node-chrome (replicas=1, SE_NODE_MAX_SESSIONS=2)
  - Deployment selenium-node-firefox (replicas=1, maxSessions=1)
  - Deployment selenium-node-edge (replicas=1, maxSessions=1)
  - IngressRoute selenium-hub (Traefik, selenium.iamworkin.lan)

No live behavior change — server-side dry-run confirms unchanged for
hub/firefox/ingressroute, "configured" for hub-external + 3 deploys
(default-field reordering only; SSA + field managers handle the diff).

Refs: Sprint 33 morning-routine 2026-05-25 follow-up Q-MR.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

bluejay merged commit d6f4468a9c into main

2026-05-26 00:09:36 +00:00

bluejay deleted branch ops/selenium-manifests-into-argocd-2026-05-25

2026-05-26 00:09:37 +00:00

bluejay referenced this issue from a commit

2026-05-26 00:09:38 +00:00

selenium: migrate hub + 3 nodes into ArgoCD-managed manifests (#25)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: bluejay/bluejay-infra#25