You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
install-vm readiness wait and access URLs cannot work (loopback-bound kiosk proxy behind TLS) #222
#220 diagnosed and fixed this defect for the installer-test smoke recipe, but the same defect is present in the install-vm recipe and was left out of scope.
Problem
The kiosk proxy publishes hostPort 8080 on the guest's loopback only (files/k0s/manifests/kubestellar/41-kubestellar-kiosk-proxy.yaml), and it terminates TLS (files/k0s/kiosk/nginx.conf, listen 8080 ssl).
Two consequences for install-vm:
Justfile:489 uses hostfwd=tcp::8080-:8080. A QEMU/libslirp hostfwd with an unspecified guest address is delivered to the guest's DHCP address, never to 127.0.0.1, so it can never reach the loopback-bound proxy.
Justfile:499 polls plain http://127.0.0.1:8080/. Even if the forward worked, the endpoint speaks TLS, so a plaintext probe would fail.
As a result the recipe's readiness wait cannot succeed, and the access URLs it advertises on success (Justfile:509-511) are not reachable either.
Why this is filed now
Pre-existing, and deliberately out of scope for #218 / #220. It is worth tracking because #220 corrected the manifest comment that this recipe's behavior relied on, so the mismatch is now explicit in the tree.
Possible directions
Bind the kiosk proxy hostPort to the guest's external interface (changes the security posture — needs a decision), or
Activity
fix(justfile): probe install-vm kiosk readiness from inside the guest
fix(justfile): probe install-vm kiosk readiness from inside the guest…
refactor: switch OS payload to Flatcar base, drop displaced FSDK comp…