Merge pull request #84 from vsilent/support-kata-container-runtime

Support kata container runtime

Author: vsilent

CHANGELOG.md

@@ -1,5 +1,30 @@
 # Changelog
 
+## 0.1.6 — 2026-04-08
+### Added — Kata Containers Runtime Support
+
+#### Container Runtime Selection (`commands/stacker.rs`)
+- `ContainerRuntime` enum (`runc`/`kata`) with serde support and Docker runtime name mapping
+- `detect_kata_runtime()` — cached detection via `docker info` with 5s timeout and `OnceLock`
+- `inject_runtime_into_compose()` — parses compose YAML and injects `runtime:` per-service
+- `DeployAppCommand` and `DeployWithConfigsCommand` accept optional `runtime` field
+- Graceful fallback: if Kata is requested but unavailable, deploys with runc and emits `kata_fallback` warning
+- Effective runtime reported in deploy result body
+
+#### Capabilities Discovery (`comms/local_api.rs`)
+- `/capabilities` endpoint reports `"kata"` in features list when Kata runtime is detected on the host
+
+#### Code Quality Fixes (PR #84 review)
+- `runtime_compose_tests` gated with `#[cfg(all(test, feature = "docker"))]` for minimal builds
+- Replaced blocking `std::path::Path::exists()` with `tokio::fs::try_exists()` in async deploy path
+- Added proper error logging in `unlink_handler` for `try_exists` failures
+
+#### Tests
+- 14 new tests: enum behavior, serde deserialization, compose YAML injection (including edge cases), command parsing with runtime field
+
+## 0.1.5 — 2026-03-26
+### Added — Long Polling, Vault Integration, Compose Agent Sidecar
+
 ## 0.1.4 — 2026-03-13
 ### Added — CLI Improvements, Install Script & GitHub Releases
 

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "status-panel"
-version = "0.1.5"
+version = "0.1.6"
 edition = "2021"
 
 [features]

Cargo.toml

@@ -60,3 +60,36 @@
 - [ ] Expose health metrics indicating which control plane executed each command (`status_panel` vs `compose_agent`) so ops can track rollout and fallbacks.
 - [ ] Publish Vault secret schema: `secret/agent/{hash}/status_panel_token` and `secret/agent/{hash}/compose_agent_token`; refresh + cache them independently.
 - [x] Add config flag to disable compose agent (legacy mode) and emit warning log so Blog receives `compose_agent=false` via `/capabilities`.
+
+## Kata Containers Support (Stacker Server)
+**Context**: The Status Panel Agent now supports `runtime` field (`runc`/`kata`) on `deploy_app` and `deploy_with_configs` commands, detects Kata availability via `docker info`, injects `runtime:` per-service into compose YAML, and reports `"kata"` in `/capabilities` features when available.
+
+### Stacker API Changes
+- [ ] Add `runtime` field (string, optional, default `"runc"`) to `POST /api/v1/agent/commands/enqueue` payload for `deploy_app` and `deploy_with_configs` commands.
+- [ ] Add `runtime` field to the deployment model/database so per-deployment runtime preference is persisted across redeploys and restarts.
+- [ ] Validate `runtime` values on the Stacker side (`runc`, `kata`); reject unknown values with 422.
+- [ ] Read agent `/capabilities` response and store `kata` feature flag per agent; use this to prevent scheduling Kata deployments on agents that don't support it.
+
+### CLI / UI Integration
+- [ ] Add `--runtime kata|runc` flag to `stacker deploy` CLI command; pass through to the agent command payload.
+- [ ] Show runtime selection option in the deployment UI (dropdown or toggle); default to `runc`, show `kata` only if agent capabilities include it.
+- [ ] Display effective runtime in deployment detail view (agent reports `"runtime"` in deploy result body).
+- [ ] Show `kata_fallback` warnings from agent result in the UI/CLI output so users know when Kata was unavailable.
+
+### Vault / Config Management
+- [ ] Allow per-deployment runtime preference in Vault (`secret/agent/{hash}/runtime_preference`); agent can read this as a default when no explicit `runtime` is in the command payload.
+- [ ] Support org-level policy: "all deployments must use Kata" — Stacker enforces this before enqueuing commands.
+
+### J2 Template Updates
+- [ ] Update compose J2 templates to optionally include `runtime:` field per-service when Kata is requested (alternative to agent-side YAML injection for new deployments).
+- [ ] Document that `runtime:` in compose YAML and `runtime` in command payload are complementary — agent-side injection is the fallback when templates don't include it.
+
+### Host Provisioning
+- [ ] Create Ansible playbook for Kata setup: install `kata-containers`, configure `daemon.json` with Kata runtime, validate KVM access.
+- [ ] Add Terraform module for provisioning Kata-ready bare-metal hosts (Hetzner, OVH) with KVM enabled.
+- [ ] Document network constraints: Kata containers cannot use `network_mode: host`; advise `bridge` or `macvlan`.
+
+### Monitoring & Observability
+- [ ] Add Prometheus metric `agent_deploy_runtime{runtime="kata|runc"}` counter to track Kata adoption.
+- [ ] Log `kata_fallback` events in agent audit trail for ops visibility.
+- [ ] Add dashboard widget showing Kata vs runc deployment distribution across fleet.