fix(vm): restore kube-apiserver port forwarding for host-side kubectl

The previous commit (070bcca1) dropped port 6443 from the gvproxy
port_map, breaking all host-side kubectl commands including the
readiness check and stale pod recovery. k3s runs the API server
with host networking so VM:6443 is directly reachable — restore
the 6443:6443 mapping alongside the 30051:30051 NodePort mapping.
This commit is contained in:
Drew Newberry
2026-03-24 10:56:15 -07:00
parent e012e092b7
commit 9e340ea755
+6
View File
@@ -161,6 +161,12 @@ impl VmConfig {
],
workdir: "/".to_string(),
port_map: vec![
// kube-apiserver — k3s runs the API server with host
// networking so it listens on VM:6443 directly. The
// host-side readiness check (`wait_for_gateway_service`)
// and `recover_stale_pods` both use kubectl against
// 127.0.0.1:6443 via the copied kubeconfig.
"6443:6443".to_string(),
// Navigator server — with bridge CNI the pod listens on
// 8080 inside its own network namespace (10.42.0.x), not
// on the VM's root namespace. The NodePort service