Platform components
These pages describe the images and the Go module that ship with Datasance PoT on train v3.9.0. Each page says which process starts, which files it reads, and which tag this train publishes.
They are not a second control plane guide. Deployment is on Control plane and Platform deployment. The in-place upgrade from v3.8.0 is on Upgrading to v3.9.0.
Components
| Component | Pin | Where it runs |
|---|---|---|
| Operator | ghcr.io/datasance/operator:3.9.0 | Kubernetes. Reconciles a ControlPlane custom resource. |
| Router | ghcr.io/datasance/router:3.9.0, embedded Skupper Router 3.5.3 | Kubernetes, and as a system microservice on an Edgelet node. |
| NATS Server | ghcr.io/datasance/nats:2.15.0, upstream nats-server 2.15.0, entrypoint iofog-nats | Kubernetes hub, and as a system microservice on an Edgelet node. |
| Go SDK | github.com/eclipse-iofog/iofog-go-sdk/v3, Go 1.26.6 or newer | A library. potctl and the operator call it. |
Where they run
On Kubernetes, the operator reconciles a ControlPlane custom resource.
On a remote control plane and on a local control plane, potctl deploys the Controller through Edgelet. The Controller starts router and nats as system microservices.
Application workloads are not operator objects. Create them with potctl, the REST API, EdgeOps Console, or the Go SDK after the control plane is up.
See anything wrong with the document? Help us improve it!