9fe15c33

docs: multi-tenancy in v0.0.1 scope, and v0.0.3 candidates

a73x 2026-08-06 09:12

Commit message

docs: multi-tenancy in v0.0.1 scope, and v0.0.3 candidates

A second tenant on the fleet joins the v0.0.1 scope: the seam is live, and
what remains is the per-tenant user-CA split, SSE/console/event isolation,
tenant-scoped audit, and cross-tenant token mint.

v0.0.3 opens with provider integration — provisioning onto cloud
infrastructure that already exists.

ROADMAP.md

Old		New
@@ -33,6 +33,13 @@ frozen from here.
33	- Quickstart: zero-to-first-VM on one host, then add a second host	33	- Quickstart: zero-to-first-VM on one host, then add a second host
34	- Upgrade guide, release notes	34	- Upgrade guide, release notes
35		35
		36	Multi-tenancy
		37
		38	- A second tenant on the fleet. The seam is already live (tenants table,
		39	tenant-scoped tokens/VMs, `<tenant>.<name>` connect names); tenant #2 needs
		40	the per-tenant user-CA split, SSE/console/event isolation, tenant-scoped
		41	audit, and cross-tenant token mint
		42
36	Gate	43	Gate
37		44
38	- Clean-slate rehearsal: the quickstart followed verbatim on a fresh host,	45	- Clean-slate rehearsal: the quickstart followed verbatim on a fresh host,
@@ -47,3 +54,8 @@ running guests, new features.
47	(Virtualization.framework backend)	54	(Virtualization.framework backend)
48	- Live cloud-hypervisor handover for running guests	55	- Live cloud-hypervisor handover for running guests
49	- Public gateway: route inbound traffic to guest services through eitri	56	- Public gateway: route inbound traffic to guest services through eitri
		57
		58	## v0.0.3 - candidates
		59
		60	- provider integration: provision on existing cloud infrastructure
		61	- aws, gcp, proxmox, etc