Nexo Manager
Nexo Manager is the in-cluster agent for a Nexo environment. It connects outbound to the Control Plane, reports runtime inventory, receives commands, and coordinates Nexo resources in Kubernetes. It is not in the MongoDB traffic path.
0.2.0 artifact identity
| Item | 0.2.0 value |
|---|---|
| Nexo Edge chart | 0.2.0 |
| Manager image tag | 20260613.371-384b887 |
| Source revision encoded by tag | 384b887 |
| Public image digest | Not published in these docs |
The image tag identifies the chart-pinned build but is not an immutable substitute for the missing release digest.
Responsibilities
| Responsibility | 0.2.0 behavior |
|---|---|
| Environment identity | Validates the connect token and identifies the registered cluster/environment. |
| Heartbeat | Reports Manager version, configured Proxy image, managed Proxy count, deployment inventory, and cluster metadata. |
| Deployment execution | Applies approved CRD manifests or legacy workload configuration. |
| Fleet lifecycle | Handles deploy, Proxy rollout, bundle-upgrade command, and uninstall command classes. |
| Acknowledgement | Reports applied or failed to the Control Plane. |
Command lifecycle
- Manager heartbeats to the Control Plane.
- The Control Plane returns commands.
- Manager applies the operation.
- Manager acknowledges success or failure.
The 0.2.0 heartbeat does not report bundle version, supported CRD kinds, pipeline reference kinds, CRD schema fingerprint, or Manager protocol capabilities. It also does not support connect-token rotation. Do not attribute those later designs to this immutable snapshot.
Upgrade limitation
Manager contains an upgrade command handler, but no public self-service 0.2.0 upgrade procedure is supported. Use only an approved Nexo console or support-directed workflow; do not invoke component or Helm upgrade internals directly.