Glossary
Definitions for terms used across this documentation set, as they apply to the current 0.2.0 Private Preview release. Where a term's behavior differs by release, the definition says so — always confirm against the compatibility reference for your specific bundle.
Admission
A Kubernetes API server control (an admission webhook) that validates or rejects mutations to managed Deployments and Nexo custom resources before they persist. See Admission and drift behavior.
Bundle (release bundle)
An immutable, versioned, tested combination of the Nexo Edge chart, Manager, Operator, and Proxy images released together — the unit customers install, upgrade, and roll back as a whole. Distinct from a support bundle (below). See Manager versions.
Connection phase
A conceptual phase for policy that would run once per client connection before MongoDB
commands are processed. NexoConnectionPipeline records TLS, handshake, tenant identity,
pooling, and limit intent as validation and graph metadata, but the current Operator does
not deliver those fields to the runtime. Supported TLS is configured on
NexoDeploymentProfile. See Connection pipeline operations
reference.
Control Plane
The Nexo SaaS service that handles identity and tenancy, environment registration, configuration revisions, release orchestration, license state, and operational status. It is not in the MongoDB request path. See Control plane and data plane.
CRD (Custom Resource Definition)
A Kubernetes API extension that defines a new resource kind. Nexo installs CRDs in the
nexo.io API group (for example NexoProxy, NexoPipeline, NexoConnectionPipeline).
Installing a CRD's schema does not by itself mean the Operator reconciles that kind — see
schema-only below and the CRD catalog.
Edge (Nexo Edge)
The customer-hosted chart that bundles Manager, Operator, and the Proxy runtime into one installable unit for a Kubernetes cluster. See Installation and deployment modes.
Entitlement vs. runtime availability
Entitlement is a tier/licensing flag that says a component is included in your plan. It is not evidence that the component executes, reconciles, or is safe to treat as an active control in the selected release — always confirm actual runtime behavior against the component catalog and compatibility reference before relying on an entitled component operationally.
Environment
A registered Kubernetes cluster binding within a project, with its own identity, status, labels, version pin, and runtime inventory. Deployments target an environment and an approved namespace within it. See Platform hierarchy and onboarding.
Ineffective
A documentation status meaning a component or field is accepted by validation and may even be reconciled, but does not change runtime behavior in the current release — for example because two configuration contracts disagree. Distinct from schema-only (never reconciled) and unsupported (no contract at all). See the component catalog for per-component status.
Manager
The customer-hosted agent that maintains the authenticated management connection to the Control Plane, applies approved desired state, and reports heartbeat inventory and acknowledgements back. See Manager.
Operator (Nexo Operator)
The Kubernetes reconciliation engine that watches Nexo custom resources, validates their desired graph, and continuously converges generated Deployments, Services, ConfigMaps, and referenced Secrets toward the approved state. See Nexo Operator.
Pipeline phase
One of the stages a MongoDB operation passes through inside a Proxy: connection (before any command), request (before the command reaches MongoDB), router (at most one router component, choosing a path such as Traffic Split or Tenant Isolation), and response (after MongoDB replies, before the client receives it). See Pipeline ordering.
Pipeline revision
A specific, versioned instance of a NexoPipeline graph. Operators compare the desired
revision against the runtime's active graph revision to confirm a change took effect, and
record the active revision before making further changes so they have a rollback target.
See Upgrade and rollback.
Project
A logical grouping of pipeline configuration, deployment intent, and revision history within an organization/team, bound to one or more environments. See Platform hierarchy and onboarding.
Proxy
The running workload that terminates MongoDB wire-protocol connections, executes the
configured pipeline, and forwards traffic to the MongoDB upstream. Deployed and managed
as a NexoProxy custom resource.
Reconciliation
The Operator's continuous process of comparing desired custom-resource state against running Kubernetes resources (Deployments, Services, ConfigMaps, Secrets) and converging them. A CRD schema can be installed without the Operator reconciling it — see schema-only.
Request / response phase
See Pipeline phase above. Request-phase components run before a command reaches MongoDB (filtering, rate limiting, rewriting); response-phase components run after MongoDB replies (masking, logging, metrics).
Router phase
See Pipeline phase above. In 0.2.0, router-phase execution is not active — a configured router component (Traffic Split, Tenant Isolation) is not evidence of an active data-path control in this release. See Pipeline ordering.
Schema-only
A documentation status meaning a CRD's schema is installed and accepted by the Kubernetes API server, but the chart-pinned Operator does not reconcile that kind in the current release — configuring it has no runtime effect. See the CRD catalog for the current reconciled-versus-schema-only matrix.
Support bundle
An archive generated by nexoctl support-bundle generate containing Kubernetes state,
logs, events, and configuration for troubleshooting. Distinct from a bundle (release
bundle, above). Built-in redaction is best-effort and requires manual review before
sharing — see Support.
Unsupported (legacy concept)
A capability that has no canonical entitlement and no supported deployment contract in any current release — historical dashboard documentation may describe it, but it cannot be deployed, reconciled, or relied on. See the dashboard-manifest-only concepts in the component catalog for the current list.