Platform Components
These pages document the in-house images and libraries that ship with Eclipse ioFog platform train v3.8.0. They wrap upstream projects where needed and integrate with the Controller, Edgelet nodes, and Eclipse ioFog YAML kinds.
Use this section when you need version pins, install paths, runtime contracts, or source repo links. For deployment walkthroughs, see Platform deployment. For architecture context, see Architecture.
Components
| Component | Version | Role |
|---|---|---|
| Operator | v3.8.0 | Reconciles ControlPlane custom resources on Kubernetes |
| Router | v3.8.0 (Skupper 3.5.1) | Cross-network messaging between Controller and Edgelet nodes |
| NATS Server | 2.14.3 upstream | Pub/sub, JetStream, and account resolver for the ECN |
| ioFog Go SDK | v3.8.0 | Build microservices (microservices), call the REST API (client), or deploy YAML (apps) |
Where they run
On Kubernetes, the Operator deploys Controller, Router, and NATS from a ControlPlane custom resource. Image tags and replicas live in Control Plane YAML.
On remote hosts, iofogctl deploys Controller, Router, and NATS from Control Plane YAML. Edgelet nodes run edge Router instances and connect back to the interior Router on the Control Plane.
Application workloads are not deployed by the Operator. Use iofogctl, the REST API, EdgeOps Console, or the Go SDK to create Application and Microservice resources after the Control Plane is up.
Related docs
| Topic | Page |
|---|---|
| Control Plane images and replicas | Control Plane YAML |
| Router and NATS TLS | Certificates Manager |
| NATS account and user rules | NATS Account Rule, NATS User Rule |
| Greenfield migration from v3.7 | Migrating to v3.8.0 |