k.rennerandClaude Opus 4.7
765b252b7b
Replaces the Kasm-VM-based test harness (blocked by VM 124's localStorage-vs-cookie auth mismatch inside Kasm's reverse-proxy configuration) with a single-container kasmweb/firefox pod running directly in the K8s cluster. - Deployment runs kasmweb/firefox with 500m/1Gi requests, 4Gi cap, 512Mi tmpfs shm, baseline capability set matching other apps. - ClusterIP Service fronts the container's HTTPS port 6901. - Ingress exposes browser.k.renner.uno + browser.renner.uno (both via the standard test-domain pattern) with backend-protocol=HTTPS + ssl-verify=off so nginx accepts the self-signed cert baked into the kasmweb image. proxy-read/send timeouts raised to 3600s for long-running noVNC sessions. - letsencrypt-staging issuer, matching the rest of the test stack. The pod's /etc/resolv.conf uses cluster CoreDNS, so *.renner.uno resolves to 10.2.40.80 (ingress LB) via the coredns-config template plugin. Zero per-hostname maintenance; any newly-added ingress is immediately browseable from this pod. Default VNC_PW is "kasm"; rotate via env edit. Sessions are stateless — nothing to back up. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>