Deployment topologies

Nexo 0.2.0 supports a licensed, customer-managed Kubernetes Private Preview installation. The authenticated console supplies a version-pinned Helm command and registry credential workflow.

0.2.0 topology

Component	0.2.0 role
Hosted Control Plane	Desired state, environment identity, commands, licensing, and status
Manager 20260613.371-384b887	Heartbeat, command execution, acknowledgement, and runtime inventory
Chart-pinned Operator	Reconcile 18 registered Nexo kinds and generated resources
Chart-pinned Proxy	Execute supported request/response phases and direct target egress
Customer MongoDB	Authentication, authorization, data, topology, backup, and availability

The Manager heartbeat does not report bundle version, supported kinds, pipeline reference kinds, schema fingerprint, or later protocol capabilities.

Connection lifecycle

Proxy accepts the connection, processes supported MongoDB OP_MSG traffic, passes authentication to MongoDB, executes supported request components, connects to NexoProxy.spec.targetAddress, executes supported response components, and returns the reply. The router and connection phases are rendered but not executed.

Available deployment shapes

Manager-managed Kubernetes

This is the supported installation and lifecycle path. Use the console-generated command; do not reconstruct chart locations or tags from legacy documentation.

Isolated evaluation

Use a dedicated namespace and disposable MongoDB fixture to validate the bundle. An evaluation deployment is not evidence of production readiness.

Shared Service

Multiple clients may connect to a Proxy Service if the customer's network, policy, and blast-radius design permits it. No separate 0.2.0 shared-pool product contract exists.

Unavailable modes

• public standalone binary, VM, or bare-metal installation;
• Docker or Docker Compose distribution;
• manual or automatically injected application sidecar;
• public Helm repository;
• self-hosted Control Plane;
• public air-gapped installation;
• Nexo-hosted database traffic.

Rollout model

The hosted service sends an authorized operation to Manager. Manager applies approved resources, Operator reconciles the supported graph, and Proxy reports runtime state. Verify the active graph revision. The 0.2.0 Proxy controller does not watch NexoTrafficSplit, NexoTenantIsolation, NexoQuerySizeLimit, or NexoVersionCompat; edits require approved reconciliation of the owning NexoProxy.

Legacy examples

Retired get.nexo.io, Docker, charts.nexo.io, api.nexo.io, self-hosted Control Plane, and sidecar commands are historical examples only and must not be used to install 0.2.0.

This includes the minimal nexo-proxy command, public Manager Helm command, self-hosted-Control-Plane Helm command, and manual sidecar arguments. The only supported replacement is the authenticated 0.2.0 console-generated Kubernetes workflow.