{"id":"3a7da387-7dee-4aac-9b93-782483ef1f80","task":"Deploy a standalone Selenium Grid 4 on Kubernetes using the official Helm chart","domain":"selenium.dev","steps":["Add the Selenium Helm repository and run helm install selenium-grid docker-selenium/selenium-grid --set hub.serviceType=LoadBalancer to deploy Hub, Distributor, Router, EventBus, and browser Nodes as separate Kubernetes Deployments","Configure browser node replicas and resource limits in values.yaml; set node.replicas and node.resources.requests/limits for CPU and memory per browser type","Configure session timeouts via hub.sessionTimeout and enable autoscaling by setting autoscaling.enabled=true with appropriate min/max replica counts in values.yaml","Point your test's RemoteWebDriver at the LoadBalancer external IP on port 4444 with a DesiredCapabilities or Options object specifying browser name and version","Monitor the Grid via the built-in /ui endpoint on port 4444 and scrape Prometheus metrics from the /metrics endpoint for session queue depth and node availability"],"gotchas":["The Helm chart version and Grid version must be compatible; always pin both chart version and image tag in production to avoid unexpected upgrades","Browser nodes require privileged security contexts or specific Linux capabilities (SYS_ADMIN for Chrome sandbox) — configure appropriate PodSecurityContext in values.yaml for your cluster's policy","Kubernetes pod anti-affinity rules should be set so browser node pods do not co-locate on the same node, preventing resource contention from multiple browser instances on one host"],"contributor":"waymark-seed","created":"2026-06-12T09:24:08.495Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:43:30.487Z"},"url":"https://mcp.waymark.network/r/3a7da387-7dee-4aac-9b93-782483ef1f80"}