Skip to main content
Version: v3.9.0

Upgrading to v3.9.0

Platform train v3.9.0 supports an in-place upgrade from v3.8.0. You keep the same Controller database, refresh control plane image tags, roll Edgelet v1.1.0 on fleet nodes, and upgrade potctl on your workstation.

Not supported: v3.7 or older → v3.9

There is no direct upgrade from v3.7.x, v1.6.x, or legacy Java Agent deployments to v3.9.0. Move to v3.8.0 first with a greenfield Control Plane and Edgelet-only nodes. See Migrating to v3.8.0 and the Documentation archive.

Before you start​

  1. Read What's New for YAML and API changes that affect registries, microservices, and Edgelet node manifests.
  2. Export or commit your control plane YAML, Agent manifests, and application YAML.
  3. Plan a maintenance window. Upgrade control plane components first, then fleet Edgelet nodes.
  4. Air-gapped sites: stage wrapper images before you bump tags. See Airgap deployment and Offline images.

Default pins for v3.9.0 are listed on Control plane.

Supported upgrade path​

You are onAction
v3.8.0Follow the steps below (same database).
v3.7.x or olderGreenfield to v3.8.0 first. See Migrating to v3.8.0.
New installDeploy v3.9.0 directly. See Getting started or Platform deployment.

Keep Controller, Operator (Kubernetes), Router, NATS, system Edgelet on Controller hosts, fleet Edgelet nodes, and potctl on the same train.

  1. Upgrade potctl on your workstation to v3.9.0.
  2. Bump image tags and Edgelet pins in control plane YAML (Controller, Router, NATS, spec.systemAgent, Console pin if overridden). Use the defaults on Control plane.
  3. Re-apply control plane YAML with deploy:
potctl deploy -f controlplane.yaml

On Kubernetes, upgrade the operator release or Helm chart on the 3.9.0 train, then apply the updated KubernetesControlPlane manifest.

  1. Upgrade fleet Edgelet nodes to 1.1.0 after the control plane is healthy. See Upgrade and rollback Edgelet. Controller hosts use the system node path in step 3.
  2. Review workloads and config in EdgeOps Console or with describe. Update registry rows to type: oci or type: hf, refresh microservice container blocks if you adopt new v3.9 fields, and deploy Model / Knowledge catalog rows before binding them in microservices.

Detailed Console and CLI notes live in Upgrade the platform train.

Verify​

potctl describe controlplane
potctl describe controller CONTROLLER_NAME
potctl get agents

The console Overview shows control plane status.

Rollback​

If you must roll back, redeploy the previous control plane YAML tags and Edgelet pins, then downgrade fleet nodes with the same upgrade agent flow targeting the prior Edgelet version. Test rollback in a lab ECN before you change production.

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

Edit this page on GitHub!