Controller
Greenfield release: v3.8.0
Platform train v3.8.0 needs a fresh Controller database, Edgelet v1.0.0+ on every node, and potctl v3.8.0. There is no in-place upgrade from v3.7. See Migrating to v3.8.0.
The Controller is the control plane for Datasance PoT. It tracks Edgelet nodes, applications, microservices, routes, and platform services (router, NATS) across your Edge Compute Network (ECN).
Small ECNs often run one Controller. You can run multiple Controllers for resiliency. Each Controller needs a network path every Edgelet node can reach (static IP, DNS, or load balancer).
Default portsâ
| Service | Default port | Purpose |
|---|---|---|
| Controller REST API | 51121 | /api/v3/... for potctl, SDK, and automation |
| EdgeOps Console | 8008 | Web UI embedded in the Controller image |
What you use it forâ
- Provision and manage Edgelet nodes (YAML
kind: Agent) - Deploy applications and microservices
- Configure routes, services, registries, and catalog entries
- Open exec and log sessions (WebSocket, multi-session)
- Authenticate users via embedded OIDC (default) or an external IdP
Manage the ECN with potctl, the EdgeOps Console, or the REST API.
Requirementsâ
- Node.js 24.x for development and CI builds of the Controller image
- Edgelet v1.0.0+ on every edge node (legacy Java Agent and v3.7 field agents are not supported)
- A new database on first install (no v3.7 â v3.8 migrator)
Reference pagesâ
| Document | Description |
|---|---|
| Configuration | YAML config, TLS, OIDC, Console, and environment variables |
| REST API | v3.8 API paths, breaking changes, and OpenAPI |
| Embedded OIDC | Default auth mode for greenfield deployments |
| EdgeOps Console | Web UI for day-2 cluster operations |
| Edgelet exec sessions | WebSocket exec model and session limits |
See anything wrong with the document? Help us improve it!