Nexo Manager versions

Nexo Manager is versioned as a component, but customers deploy it as part of an immutable Nexo Edge release bundle. Always use the bundle version as the customer upgrade target and the Manager image digest as the exact component identity.

Version identifiers

Identifier	Purpose	Authoritative source
Nexo bundle version	Customer-facing install, upgrade, rollback, and compatibility contract	Published release bundle and Nexo Edge chart appVersion
Manager image tag	Human-readable build identifier	Release bundle manager_image.tag
Manager image digest	Immutable Manager artifact identity	Release bundle manager_image.digest
Manager binary version	Build version reported by nexo-manager --version and heartbeat	Manager build metadata
Manager Helm chart version	Packaging version for the standalone chart	Chart metadata; not the Nexo compatibility contract

Do not infer compatibility from the standalone Manager chart version or from an image tag alone. A supported release must identify the complete bundle and immutable image digests.

Private Preview baseline

The current documentation is a Private Preview baseline, not a stable product release.

• The verified Nexo Edge chart interface is 0.2.0.
• The chart pins Manager tag 20260613.371-384b887.
• No immutable Manager image digest is published in these docs.
• Licensed evaluators should obtain the release-specific bundle manifest before installation or upgrade.
• Legacy standalone Manager chart metadata in source repositories is not a supported release declaration.

Current heartbeat reporting

Manager heartbeat reports:

• Manager binary version;
• proxy version;
• managed Proxy count and deployment inventory;
• cluster metadata;
• Manager protocol version and named capabilities on the Next source line.

The current heartbeat does not report the installed bundle version, complete custom resource kind set, accepted pipeline reference kinds, or CRD schema fingerprint. Those fields remain requirements for a future digest-complete compatibility contract.

Upgrade rules

1. Select an approved Nexo bundle version, not a raw Manager image tag.
2. Confirm the target bundle and exact component artifacts through release metadata.
3. Review Manager-specific changes, required CRD migrations, and rollback constraints.
4. Use only the approved console or support-directed upgrade workflow.
5. Verify Manager and Proxy versions, deployment inventory, and data-path health after rollout.

Do not hand-patch the Manager Deployment during a normal upgrade. Doing so bypasses the bundle compatibility and rollback model.

Manager release-note contract

Every published release must include a Manager entry stating:

• image tag and digest;
• binary version and source commit;
• supported Nexo bundle versions;
• added or removed CRD kinds;
• CRD schema compatibility changes;
• control-plane API or heartbeat changes;
• upgrade and rollback requirements;
• security fixes and known issues.

See What's New, Compatibility, Upgrade and rollback, and Breaking changes and deprecations.