Drew Newberry e012e092b7 fix(vm): fix gateway readiness timeout with correct port mapping and aligned pre-bake ...

Two issues caused the gateway service readiness check to time out:

1. Port mapping mismatch: gvproxy mapped host:30051 → VM:8080, but with
   bridge CNI the pod listens on 8080 inside its network namespace, not
   on the VM's root namespace. Changed to 30051:30051 so traffic flows
   through the NodePort service (kube-proxy nftables → pod:8080).

2. Pod cycling from helm upgrade: build-rootfs.sh pre-baked with
   hostNetwork=true and automountServiceAccountToken=false, but
   gateway-init.sh changed these at boot, triggering a HelmChart
   reconcile that killed the pre-baked pod ~90s in. Aligned pre-bake
   values (hostNetwork=false, automountServiceAccountToken=true) to
   match runtime, eliminating the manifest delta.

2026-03-24 10:32:30 -07:00

..

api-proxy.py

feat(vm): add navigator-vm crate with libkrun microVM and k3s gateway

2026-03-16 10:41:53 -07:00

build-rootfs.sh

fix(vm): fix gateway readiness timeout with correct port mapping and aligned pre-bake

2026-03-24 10:32:30 -07:00

check-vm-capabilities.sh

feat(vm): add custom libkrunfw runtime with bridge CNI and netfilter support

2026-03-23 22:08:30 -07:00

gateway-init.sh

fix(vm): resolve CNI bridge and nftables errors for reliable pod networking

2026-03-24 10:22:53 -07:00

hello-server.py

feat(vm): add navigator-vm crate with libkrun microVM and k3s gateway

2026-03-16 10:41:53 -07:00

verify-vm.sh

fix(vm): resolve CNI bridge and nftables errors for reliable pod networking

2026-03-24 10:22:53 -07:00