📄️ Architecture
The single-port multi-tenant model for an EDK enterprise deployment, the operator and tenant host scheme, the gateway contract, and the host-and-path routing table every fronting layer must satisfy.
📄️ Install on Docker
Run the EDK enterprise stack behind a single-port Traefik gateway with Docker Compose, using local wildcard DNS through saas.localtest.me and a local wildcard TLS certificate.
📄️ Install on Kubernetes (Cilium)
Deploy the EDK enterprise stack on Kubernetes behind the Cilium Gateway API, with one wildcard HTTPS listener, wildcard TLS through cert-manager DNS-01 or a TLS secret, and the edk-enterprise Helm gateway values.
📄️ Cloud load balancers
How AWS ALB, GKE Gateway, and Azure Application Gateway conform to the single-port EDK gateway contract, with the one configuration gotcha for each platform and the edk-enterprise example values that encode it.
📄️ Local multi-domain development
Develop against the single-port multi-tenant EDK locally with saas.localtest.me wildcard DNS, expose the stack to a real phone wallet through an ngrok wildcard or a Cloudflare Tunnel, or serve it from a domain you control with a publicly trusted Let's Encrypt certificate.
📄️ Provisioning and onboarding
Two paths to a fully onboarded EDK platform with its first tenant, an interactive UI path and a scripted REST path through the deployment repository provision script, both producing the same documented end state locally and in production.