Adolfo Delorenzo 4fc078f7a3 fix: kubeconfig server accessible via port forwarding, integration tests use proper auth ...

Bind kubeconfig HTTP server to 0.0.0.0:8080 (was 127.0.0.1) so integration
tests can reach it via QEMU SLIRP port forwarding. Add shared wait_for_boot
and fetch_kubeconfig helpers to qemu-helpers.sh. Update all 5 integration
tests to fetch kubeconfig via HTTP and use it for kubectl authentication.

All 6 tests pass on Linux with KVM: boot (18s), security (7/7), K8s ready
(15s), workload deploy, local storage, network policy.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-12 15:25:32 -06:00

..

benchmark

fix: kernel AppArmor 2-pass olddefconfig and QEMU test direct kernel boot

2026-02-12 14:11:38 -06:00

integration

fix: kubeconfig server accessible via port forwarding, integration tests use proper auth

2026-02-12 15:25:32 -06:00

kernel

feat: initial Phase 1 PoC scaffolding for KubeSolo OS

2026-02-11 10:18:42 -06:00

lib

fix: kubeconfig server accessible via port forwarding, integration tests use proper auth

2026-02-12 15:25:32 -06:00

qemu

fix: kernel AppArmor 2-pass olddefconfig and QEMU test direct kernel boot

2026-02-12 14:11:38 -06:00