What's New in Datasance PoT

Upgrade from v3.8.0

v3.9.0 is an in-train upgrade on the same Controller database. Bump control plane image tags, roll Edgelet v1.1.0 on nodes, and upgrade potctl to v3.9.0.

See Upgrading to v3.9.0. v3.7.x and older still require a greenfield move to v3.8.0 first: Migrating to v3.8.0.

Platform train v3.9.0 ships Controller v3.9.0, potctl v3.9.0, Edgelet v1.1.0, EdgeOps Console v1.1.0, ioFog Operator v3.9.0, and updated Router and NATS wrapper images. Pair every component on the same train.

• Platform train v3.9.0 pins Controller, Edgelet, Console, and messaging wrappers for in-place upgrades from v3.8.
• AI Model Catalog stores fleet LLM weights from Hugging Face Hub or OCI artifacts. Attach to Edgelet nodes and bind in spec.models.
• AI Knowledge Catalog stores RAG datasets and document bundles. Bind in spec.knowledge on microservices.
• Registries (oci / hf) replace legacy TLS cert flags with type, ca, and insecure.
• Microservice container fields add limits, security context, devices, tmpfs, entrypoint, and volume scope options for production workloads.
• Edgelet v1.1.0 is required on every node. Agent YAML drops HAL scan fields; use edgeGuardFrequency for attestation when needed.
• EdgeOps Console v1.1.0 adds editors for AI catalogs, models attach state, and v3.9 cluster config flows.
• NATS Server 2.15.0 wrapper upgrade with the same volume-mount contract as v3.8.
• Router wrapper v3.9.0 embeds Skupper Router 3.5.3.
• Upgrade and migration paths summarize who can move in place vs greenfield.
• v3.8 foundation (Edgelet-only nodes, embedded OIDC, WebSocket exec) remains documented in the v3.8.0 snapshot.

Platform train v3.9.0

Component	v3.9.0 default
PoT platform	v3.9.0
Controller	v3.9.0
potctl	v3.9.0
ioFog Operator	v3.9.0
Router (wrapper image)	v3.9.0 (Skupper 3.5.3 inside)
NATS (wrapper image)	2.15.0 (upstream NATS 2.15.0)
Edgelet	v1.1.0
EdgeOps Console	v1.1.0
Go SDK	v3.9.0

Override tags in control plane YAML when you need a hotfix pin. Defaults and YAML keys: Control plane. Step-by-step upgrade: Upgrading to v3.9.0 and Upgrade the platform train.

AI Model and Knowledge catalogs

v3.9 adds fleet kind: Model and kind: Knowledge resources. The Controller pulls weights or datasets from type: hf or type: oci registries, tracks attach state per Edgelet node, and mounts ready content into microservices.

Catalog	Purpose	Microservice bind
Model	LLM and inference weights (GGUF, safetensors, OCI model-spec)	spec.models.items[]
Knowledge	RAG corpora, Hub datasets, OCI document bundles	spec.knowledge.items[]

Console path: Config → AI Model Catalog and Config → AI Knowledge Catalog. CLI: deploy, describe model, attach model, and the matching knowledge commands.

Edgelet nodes can also hold local edgelet.iofog.org/v1 models for lab workflows. Fleet operators usually use the Controller catalog.

Find out more!, AI Knowledge Catalog, and Microservices - models and knowledge.

Registries (OCI and Hugging Face)

Registry rows now declare a backend with spec.type: oci (container registries) or hf (Hugging Face Hub). Private Hub pulls use a token in password.

v3.9 removes requiresCert, certificate, and isSecure. Use optional ca (PEM or base64) and insecure for lab TLS instead.

Microservices and catalog items reference registries by numeric ID or aliases remote / local.

Find out more! and Catalog microservices.

Microservice container fields

spec.container on microservices expands for parity with OCI runtime options:

• Resource limits: cpus, memoryReservation, memorySwap, shmSize
• Security: runAsGroup, readOnlyRootFilesystem, capAdd / capDrop
• Devices and mounts: devices, tmpfs, cdiDevices, volume scope for named volumes
• Process: workingDir, entrypoint, commands, ulimits, sysctls

Wasm and alternate runtimes still use container.platform and container.runtime with runtime classes.

Find out more! and Microservice fields.

Edgelet v1.1.0

Edgelet v1.1.0 pairs with Controller v3.9.0. Upgrade fleet nodes after you roll the control plane. Default image: edgelet:1.1.0 on your flavor registry.

Agent YAML changes in v3.9:

• Removed: deviceScanFrequency, bluetoothEnabled, abstractedHardwareEnabled
• Use edgeGuardFrequency when you need hardware attestation (EdgeGuard)

Upgrade on a node:

sudo sh /usr/share/edgelet/install.sh --upgrade --version=v1.1.0

Or use upgrade agent as described in Upgrade and rollback Edgelet.

Find out more!, Edgelet introduction, and Edgelet management.

EdgeOps Console v1.1.0

EdgeOps Console v1.1.0 ships embedded in the Controller image (default port 8008). v3.9 adds first-class UI for AI catalogs, registry type editing, and refreshed console flows aligned with the Learn guides.

Open with potctl view or controller.consoleUrl.

Find out more!, Console features, and Operate overview.

NATS and Router pins

NATS wrapper image tag 2.15.0 pins upstream NATS Server 2.15.0. Config volume paths and JWT provisioning match v3.8.

Router wrapper image tag 3.9.0 embeds Skupper Router 3.5.3 (v3.8 used Skupper 3.5.1).

Find out more!, Router, and Message bus in Learn.

Upgrade and migration paths

Starting version	Path
v3.8.0	In-place upgrade: Upgrading to v3.9.0
v3.7.x or v1.6.x	Greenfield to v3.8 first: Migrating to v3.8.0, Documentation archive
Greenfield v3.9	Quick start (local) or Platform deployment

After upgrade, reconcile stalled platform microservices on Controller hosts if Router or NATS pods look stale: Reconcile.

v3.8 foundation

PoT v3.8.0 introduced Edgelet-only nodes, embedded OIDC, EdgeOps Console in the Controller image, WebSocket exec, multi-arch images[] catalogs, and the greenfield migration from v3.7. That behavior still applies on v3.9; the v3.8.0 docs snapshot keeps the full v3.8 release narrative and greenfield warnings.

New to the platform? Start with Welcome, Learn, and the Acme Smart Plant tutorial on pot-edge-patterns v1.1.0 images.

CLI and Go SDK

potctl v3.9.0 adds catalog commands for Model and Knowledge, registry describe output with type, and deploy validation for v3.9 YAML. Config directory remains ~/.iofog/v3.

Go SDK v3.9.0 tracks the same Controller API and catalog kinds.

Find out more!, potctl getting familiar, and Go SDK.

See anything wrong with the document? Help us improve it!

Edit this page on GitHub!