Hugh Hackman acd53c297b fix: wait for HTTP reachability after rollout in deploy-e2e-headlamp.sh ...

kubectl rollout status confirms the pod is ready per readinessProbe, but
Kubernetes Service DNS propagation to the runner pod may lag behind.
This caused intermittent E2E failures with ERR_NAME_NOT_RESOLVED.

Add a poll loop (max 120s) after rollout status that verifies the service
URL is reachable via HTTP before writing .env.e2e. This eliminates the
race condition between DNS propagation and Playwright launch.

Fixes: PRI-687 (intermittent E2E DNS failure)

2026-03-22 04:51:30 +00:00

..

deploy-e2e-headlamp.sh

fix: wait for HTTP reachability after rollout in deploy-e2e-headlamp.sh

2026-03-22 04:51:30 +00:00

teardown-e2e-headlamp.sh

fix: replace Helm-based E2E deploy with kubectl apply

2026-03-21 20:43:25 +00:00