Nexo Operator
Nexo Operator is the Kubernetes reconciliation engine for Nexo Edge. It watches Nexo custom resources supported by the bundled build, validates their desired graph, and continuously converges generated Deployments, Services, ConfigMaps, and referenced Secrets toward the approved state.
Responsibilities
| Responsibility | What Operator does |
|---|---|
| Type registration | Registers the 18 nexo.io kinds supported by Operator build 20260611.352-008260c; six additional schemas are installed only. |
| Validation | Validates managed signatures, registered resource fields, references, and readiness before rendering workloads. |
| Graph resolution | Resolves NexoProxy, NexoDeploymentProfile, NexoPipeline, router, and supported request/response/connection step references. |
| Workload reconciliation | Creates and updates Proxy Deployments, Services, routing/step ConfigMaps, and image-pull Secret copies. |
| Drift correction | Reconciles changes continuously and reports observed generation, readiness, phase, conditions, and configuration hashes. |
| Resource ownership | Uses Kubernetes ownership relationships so generated namespaced resources follow the lifecycle of their NexoProxy. |
| Runtime composition | Renders ingress, egress, and supported step containers in the Proxy pod and mounts configured TLS Secrets. |
Features
- declarative request, response, router, and connection component references for registered kinds;
- managed-signature, field, reference, and readiness validation;
- Kubernetes status subresources and conditions;
- health, readiness, metrics, and optional leader election;
- generated workload ownership and continuous drift correction.
Installed custom resources
The Nexo Edge 0.2.0 chart installs 24 namespaced CRDs in API group nexo.io. All expose
one served and storage version, v1alpha1.
Installing a CRD does not mean the pinned Operator reconciles it. See the 0.2.0 CRD catalog for the support matrix.
0.2.0 schema baseline
NexoPipelineexposes request, response, router, and connection references, but only kinds reconciled by the bundled Operator are usable.- Six installed schemas are not reconciled by the chart-pinned Operator:
NexoConnectionPipeline,NexoEchoUntrusted,NexoFieldEncryption,NexoIndexAdvisor,NexoQueryGuard, andNexoReadWriteSplit. - CRDs carry
helm.sh/resource-policy: keep; uninstalling the Helm release intentionally retains them.
Because the API is v1alpha1, release notes must identify schema and reconciliation
changes. The 0.2.0 Manager does not report a schema fingerprint, so compatibility must be
verified against the exact chart and Operator build.