Files
k7/ROADMAP.md
G 3c80778156 Release 0.5.0
Observability, usage metering, tenants and quotas, and roles with OIDC login. A Helm chart installs K7 on a cluster you already run, API keys carry a role, and k7-agent no longer needs host privileges.
2026-10-18 23:21:48 +02:00

2.2 KiB

Project Roadmap

Where K7 is headed — for contributors and operators.


Current focus

Release engineering: keep the apt/PPA and PyPI k7-sdk pipelines current with main (PPA, GitHub .deb, and PyPI k7-sdk are 0.5.0). The published CLI deploys the signed GHCR k7-api by digest; a source checkout uses k7 install --api-image local.


Recently shipped

  • Multi-node Ansible, Longhorn topology, HA / cross-node tests
  • Cilium CNI + FQDN egress
  • API + SDK parity: pause / resume / fork
  • Snapshot lifecycle + GC; restore from VolumeSnapshot
  • CLI → API by default; k7 api / k7 dev api rebuild
  • Docker-in-VM sidecar + bench harness
  • First-class --docker (guest dockerd on k7d / k7d-fc; docker-vehicle on Kata)
  • Firecracker jailer
  • k7d-fc backend (k7d driving stock Firecracker + jailer)
  • Python SDK as k7-sdk / k7_sdk (katakate deprecated)
  • k7d backend install path (public Katakate/k7d GitHub Releases; playbook pin 0.7.0)
  • HTTPS-by-default for k7-api (Caddy sidecar, cluster CA)
  • Network security hardening: cluster-wide sandbox→platform isolation, opt-in sandbox ingress / --expose-port, Hubble, and a source-CIDR allowlist for the API NodePort. Tetragon was evaluated and rejected

Next goals

  • PPA / PyPI cut of the unreleased work (HTTPS, --docker, k7d-fc)
  • GHCR k7-api image, signed, installed by digest without a checkout (checked only after a tagged release installs from GHCR on a clean node)
  • Optional macOS CLI artifacts (tarball / Homebrew) — after the above

Future work

  • GPU passthrough support
  • Cross-node mobility of snapshots / forks for the k7d backend (kql already moves state across nodes via Longhorn)
  • AppArmor integration
  • CI/CD deployment tests on every public tag
  • TEE support; custom rootfs; persistent in-API interpreter

How to contribute

  1. Open a Discussion or Issue
  2. Reference the roadmap item
  3. See CONTRIBUTING.md

Last updated: October 2026