Previous approaches (port-forward to Service/Pod) failed with 'connection
refused' — the runner cannot tunnel to pod IPs through the API server.
Switch to LoadBalancer service type:
- After rollout, poll kubectl get svc for status.loadBalancer.ingress[0].ip
- Once assigned, poll http://<lb-ip>:80 until reachable
- Write HEADLAMP_URL=http://<lb-ip>:80 to .env.e2e
The runner pod (in the cluster) can reach LoadBalancer IPs assigned
by the cloud controller or metallb.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Chris Farhood
019366ff01