EdgeOps Console
Platform train v3.8.0 ships EdgeOps Console v1.0.9 embedded in the Controller image. Default listen port is 8008. Legacy browser UI docs live in the v3.7.3 snapshot.
EdgeOps Console is the web UI for Datasance PoT. It talks to the Controller REST API and WebSocket endpoints. You manage Edgelet nodes, applications, microservices, routes, and supporting resources without SSH on every edge device.
The Console is a static React SPA. The Controller embeds the production build/ output and writes runtime settings to controller-config.js at startup. You do not run a separate Console container in a default v3.8 deploy.
Version and pairingâ
| Item | Value |
|---|---|
| Console version | v1.0.9 |
| Controller | v3.8.0 |
| Default port | 8008 (REST API stays on 51121) |
Pair Console v1.0.9 with Controller v3.8.0 on the same platform train.
How you reach itâ
After the Control Plane is up, open the Console at the URL you set with CONSOLE_URL (or console.url in Controller YAML). You can also run:
potctl view
That opens the Console URL configured for your connected cluster.
Authentication follows the same RBAC model as potctl. Users only see namespaces their role allows. Default greenfield installs use embedded OIDC.
What still needs the CLIâ
Initial Control Plane deployment and Edgelet node provisioning still use potctl. Day-2 operations (deploy, edit YAML, exec, logs, registries, and most REST calls) work from the Console.
Reference pagesâ
| Document | Description |
|---|---|
| Configuration | CONSOLE_* env vars, consoleUrl, and auth contract |
| Features | Dashboard, workloads, exec, and API parity |
| Controller configuration | Full Controller YAML and environment variables |
| Exec sessions | WebSocket exec model used by the Console |