Control Plane connectivity and targeting

The hosted Control Plane manages the Nexo Edge 0.2.0 bundle. Manager connects outbound using an environment-bound token, reports heartbeat inventory, receives commands, and acknowledges success or failure. It is not in the MongoDB traffic path.

0.2.0 connection lifecycle

1. Register the environment in the authenticated console.
2. Install the console-generated 0.2.0 command.
3. Manager authenticates with the connect token.
4. Manager reports version, configured Proxy image, Proxy count, deployment inventory, and cluster metadata.
5. The Control Plane returns deploy, rollout, upgrade, or uninstall commands.
6. Manager applies and acknowledges the command.

The 0.2.0 heartbeat does not advertise later Manager protocol capabilities, bundle identity, supported CRD kinds, accepted pipeline references, or schema fingerprint.

Connect-token boundary

The token identifies the registered environment and belongs in the supported Kubernetes Secret. 0.2.0 does not support the later protected rotation lifecycle. If replacement is required, use the approved console or support workflow.

Targeting

Projects and environments are tenant-scoped. Environment labels and project stage selectors determine eligible deployment targets; namespace targeting is a separate authorization boundary. Use only the selector forms exposed by the 0.2.0 console. The legacy free-form AND/OR/NOT expressions are not an immutable 0.2.0 contract.

Console responsibilities

• environment registration and heartbeat status;
• pipeline revisions and deployment operations;
• project and environment access;
• license and tier enforcement;
• audit and deployment history available to the service at that time.

Unavailable legacy modes

0.2.0 does not publish a self-hosted Control Plane, local JSON-only air-gap mode, public chart repository, or stable api.nexo.io/app.nexo.io endpoint contract. The retired protobuf and settings examples are illustrative only.

The historical examples include a self-hosted Helm install, edge settings with a 30-second heartbeat, Subscribe/ReportStatus/PushMetrics RPCs, Boolean label expressions, and the older admins/operators/readers role summary. None is an immutable 0.2.0 public contract.

Interruption

Existing Proxy workloads can continue with their active configuration when the hosted management path is unavailable, subject to Kubernetes, Proxy, Operator, and MongoDB health. New commands and status acknowledgement cannot be assumed until connectivity returns.