External Tenants
Most tenants run on platform-managed infrastructure: their edge nodes join the central cluster directly. An external tenant is different. It runs its own standalone cluster, on its own hardware, and connects back to the platform over the EmberNet fabric (ArcNet and Flux).
This is the model for enterprise customers who will not put their production infrastructure under someone else's control plane, and it is what Ops calls external deployment mode.
| Model | How nodes join | Typical customer |
|---|---|---|
| Fireball-managed | Nodes join a cluster Fireball manages | Standard deployments |
| External | A standalone cluster connects to the platform | Enterprises running their own infrastructure |
From inside the tenant, the two look identical. Their users see their own nodes, their own metrics, shell access to their own hosts, and the same App Store. The distinction is invisible to them and matters only to whoever operates the platform.
Before you start
- A secure connection between the external site and the platform, set up with Fireball
- A running cluster at the external site
- The cluster connected, so it is visible to the platform
- Connectivity verified end to end, not just assumed
Step 4 is the one people skip. A cluster that connects but cannot be reached will register and then sit waiting to check in.
Get people into the tenant before you point them at the deployment. A user only sees the tenants they were invited to or mapped to through a directory group, and asking for a different tenant gets a refusal rather than data. That is the correct behavior, but a missing invitation looks like a broken deployment. See SSO Integration.
Creating one
Fireball creates external tenants from Global Command. We need a display name and a contact email for the tenant, and we handle the connection to your cluster. Fireball can onboard in bulk when you have many.
Watching it
Clusters in Global Command lists every connected cluster with its tenant, mode, status, node count, and address.
A cluster showing Disconnected is almost always a connection problem rather
than a cluster problem. Check ArcNet and
Flux status first; the cluster itself is usually fine and
simply unreachable.
How deployment differs
When a tenant is in external mode, App Store deployments are picked up by an agent on the customer's cluster rather than installed directly. The practical consequences:
- Deployments surface a Pending state while the agent syncs, which managed deployments skip
- A deployment is only as healthy as its least healthy target cluster
- Nothing is pushed at your cluster; your cluster pulls what it needs
See Ops & Clusters for reading that status.
Next steps
- Multi-Tenancy: isolation and the role model
- SSO Integration: binding users to tenants
- ArcNet: the connection this model depends on