Skip to main content
Version: v3.9.1

What's New in Datasance PoT

Upgrade from v3.9.0 or v3.8.0

v3.9.1 stays on the same Controller database. There is no schema or API change in this patch.

From v3.9.0, bump image tags and roll Edgelet v1.1.1. From v3.8.0, use the same tags and move straight to v3.9.1. You also pick up the v3.9 catalogs and registry fields.

See Upgrading to v3.9.1. v3.7.x and older still move to v3.8.0 first: Migrating to v3.8.0.

v3.9.1 is a security patch on the v3.9 train. Pair Controller v3.9.1, potctl v3.9.1, Edgelet v1.1.1, EdgeOps Console v1.1.1, Operator v3.9.1, Router v3.9.1, and NATS 2.15.1.

Platform train v3.9.1​

Componentv3.9.1 default
Platformv3.9.1
Controllerv3.9.1
potctlv3.9.1
Operatorv3.9.1
Router (wrapper image)v3.9.1 (Skupper 3.5.3 inside)
NATS (wrapper image)2.15.1 (upstream NATS 2.15.1)
Edgeletv1.1.1 (image 1.1.1)
EdgeOps Consolev1.1.1
Go SDKv3.9.1

Pins and YAML keys: Control plane. Steps: Upgrading to v3.9.1.

Security patch​

Control plane images, potctl, the operator, the Router wrapper, Edgelet, and the Go SDK are rebuilt on Go 1.26.9 for the October 2026 standard-library fixes. The Controller image also updates Express for an address-spoofing fix.

No YAML keys, environment variables, or HTTP routes change in this patch. The Controller API and Edgelet API pages stay on those paths.

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.

CatalogPurposeMicroservice bind
ModelLLM and inference weights (GGUF, safetensors, OCI model-spec)spec.models.items[]
KnowledgeRAG corpora, Hub datasets, OCI document bundlesspec.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.1​

Edgelet v1.1.1 pairs with Controller v3.9.1. Upgrade fleet nodes after you roll the control plane. Default image: edgelet:1.1.1 on your flavor registry. There is no Edgelet API change in this patch.

A later install.sh --upgrade on the host keeps the CLI flavor's Edgelet repository.

Agent YAML changes when you move from v3.8.0:

  • 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.1

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

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

EdgeOps Console v1.1.1​

EdgeOps Console v1.1.1 ships embedded in the Controller image (default port 8008). The API tab loads Scalar instead of Swagger UI. The tab stays pinned, and the current bearer token is already applied.

v3.9 still includes editors for AI catalogs, registry type, and cluster config flows.

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.1 pins upstream NATS Server 2.15.1. Volume mounts, JWT provisioning, and NATS_* settings match v3.9.0. max_ha_assets is enforced when streams and consumers are placed, scaled, or moved. The old $GR. gateway reply prefix is gone.

Router wrapper image tag 3.9.1 embeds Skupper Router 3.5.3 (v3.8 used Skupper 3.5.1). The wrapper behavior is unchanged.

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

Upgrade and migration paths​

Starting versionPath
v3.9.0In-place tag bump: Upgrading to v3.9.1
v3.8.0In-place upgrade: Upgrading to v3.9.1
v3.7.x or v1.6.xGreenfield to v3.8 first: Migrating to v3.8.0, Documentation archive
Greenfield v3.9.1Quick 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​

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.1 images.

CLI and Go SDK​

potctl v3.9.1 keeps the v3.9 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.1 tracks the same Controller API and catalog kinds.

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

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

Edit this page on GitHub!