Nexo Manager
Nexo Manager is the in-cluster agent for a Nexo environment. It connects outbound to the hosted Control Plane, reports installed runtime state, receives authorized operations, and coordinates Nexo resources in Kubernetes. Manager is not in the MongoDB application traffic path.
Responsibilities
| Responsibility | Current behavior |
|---|---|
| Environment identity | Validates the environment-bound connect token and binds the Manager instance to the registered Kubernetes environment. |
| Heartbeat | Reports Manager version, Proxy image, managed Proxy count, deployment names/namespaces/replicas, cluster metadata, and Manager protocol capabilities. |
| Deployment execution | Applies approved CRD manifests or legacy workload configuration received from the Control Plane. |
| Fleet lifecycle | Handles deploy, Proxy rollout, bundle-upgrade command, and uninstall command classes. |
| Acknowledgement | Reports applied or failed after command execution, with bounded retries for acknowledgement delivery. |
| Resource ownership | Uses deployment ownership metadata and guarded migration behavior to avoid adopting or deleting unrelated resources. |
Features
Heartbeat inventory
The current Manager heartbeat reports:
- Manager build version;
- configured Proxy image;
- managed Proxy count;
- deployment name, namespace, and replica count;
- cluster and region metadata when discoverable;
- Manager protocol version and named orchestration capabilities.
The current Manager does not report an installed bundle version, the complete CRD
kind set, accepted NexoPipeline reference kinds, or a CRD schema fingerprint. Those are
future release-contract requirements and must not be assumed for current compatibility
preflight.
Command lifecycle
- Manager sends an authenticated heartbeat.
- The Control Plane returns zero or more commands.
- Manager applies the operation in Kubernetes.
- Manager acknowledges
appliedorfailed. - A later heartbeat reports the resulting runtime inventory.
| Command class | Current result |
|---|---|
| Deploy | Creates or updates the approved Nexo custom resources and required runtime configuration. |
| Rollout | Updates Manager-owned NexoProxy resources to the configured Proxy image tag. |
| Upgrade | Accepted by Manager, but no public self-service upgrade procedure is published for Private Preview. Use only the approved console/support workflow. |
| Uninstall | Removes the selected Manager-owned NexoProxy; Kubernetes owner references clean up generated namespaced workload resources. |
Ownership-safe operations
Manager tracks a stable resource name and owner identifier for managed deployments. Legacy resources require an explicit migration gate before Manager adopts them. This prevents a normal rollout or uninstall from silently taking ownership of unrelated resources.
Changes
Next source line
- Added Manager protocol and promotion-contract capability advertisement.
- Hardened resource ownership, migration, and uninstall behavior.
- Added retry handling for deployment acknowledgements.
These source changes are not a new customer release by themselves. A publishable release still requires a bundle version, immutable image digests, upgrade path, and release notes.
0.2.0 Private Preview
The 0.2.0 chart pins Manager build 20260613.371-384b887. That build provides heartbeat
inventory and deploy/rollout/upgrade/uninstall command handling, but it predates Manager
protocol capability advertisement and ownership migration safeguards.