NexoRouter
:::danger Reconciled schema, ineffective runtime contract
The pinned Operator writes router configuration into routing.json, but the 0.2.0 ingress does not execute that router object. It does not change the selected upstream.
:::
This page documents the 0.2.0 Private Preview. Schema acceptance, Operator reconciliation, and runtime enforcement are separate claims; the status above is authoritative.
API identity
| Property | Value |
|---|---|
| Kind | NexoRouter |
| API group | nexo.io |
| Version | v1alpha1 |
| Resource | nexorouters |
| Short name | nrouter |
| Scope | Namespaced |
| Operator support | Reconciled schema, ineffective runtime contract |
Purpose and relationships
Declares generic route-selection strategy and named targets.
It has runtime effect only when a NexoPipeline referenced by a NexoProxy includes this object in a compatible phase and the selected Operator/runtime bundle supports the contract.
Spec field reference
The table is derived from the installed Nexo Edge CRD OpenAPI schema. “Not declared” means the schema publishes no default. A missing schema description is reported explicitly rather than inferred from implementation.
| Field | Type | Required | Default | Schema description |
|---|---|---|---|---|
spec.strategy | string | No | Not declared | No description is declared in the CRD schema. |
spec.readPreference | string | No | Not declared | No description is declared in the CRD schema. |
spec.metadata | object | No | Not declared | No description is declared in the CRD schema. |
spec.routes | array<object> | No | Not declared | No description is declared in the CRD schema. |
spec.routes[].match | string | Yes | Not declared | No description is declared in the CRD schema. |
spec.routes[].target | string | Yes | Not declared | No description is declared in the CRD schema. |
Status fields and conditions
| Field | Type | Required | Default | Schema description |
|---|---|---|---|---|
status.ready | boolean | No | Not declared | No description is declared in the CRD schema. |
status.observedGeneration | integer (int64) | No | Not declared | No description is declared in the CRD schema. |
status.configHash | string | No | Not declared | No description is declared in the CRD schema. |
status.conditions | array<object> | No | Not declared | No description is declared in the CRD schema. |
status.conditions[].type | string | No | Not declared | No description is declared in the CRD schema. |
status.conditions[].status | string | No | Not declared | No description is declared in the CRD schema. |
status.conditions[].reason | string | No | Not declared | No description is declared in the CRD schema. |
status.conditions[].message | string | No | Not declared | No description is declared in the CRD schema. |
status.conditions[].lastTransitionTime | string (date-time) | No | Not declared | No description is declared in the CRD schema. |
status.conditions[].observedGeneration | integer (int64) | No | Not declared | No description is declared in the CRD schema. |
A Ready or configHash value proves that the Operator accepted/hashed the object; it does not by itself prove runtime execution or policy enforcement.
Reconciliation and watch behavior
The registered controller validates the resource and records status. Data-path changes are applied only when the relevant NexoProxy controller rebuilds or reloads the owning graph.
The pinned NexoProxy watch maps this resource to a Proxy only through an ownerReference whose apiVersion is nexo.io/v1alpha1 and kind is NexoProxy. Without that ownership link, editing the component does not enqueue the Proxy.
Runtime execution effect
The pinned Operator writes router configuration into routing.json, but the 0.2.0 ingress does not execute that router object. It does not change the selected upstream.
Example
Use placeholders and validate in a non-production namespace first. For schema-only or ineffective kinds, this example is for schema inspection only and must not be used as evidence of enforcement.
apiVersion: nexo.io/v1alpha1
kind: NexoRouter
metadata:
name: <router-name>
namespace: <namespace>
spec:
strategy: <supported-strategy>
routes:
- match: <match-expression>
target: <named-upstream>
Update and reconciliation caveats
- Apply component and pipeline changes before expecting the owning NexoProxy graph to change.
- Check metadata.generation, status.observedGeneration when present, and the owning Proxy graphRevision/appliedRevision after every update.
- A successful kubectl apply proves only schema admission; inspect Operator conditions, generated configuration, rollout state, and runtime behavior separately.
Release-specific limitations
- The API is v1alpha1 and has no conversion webhook or second served version.
- The CRD schema is retained by Helm and can outlive the Operator release that installed it.
- This immutable page describes Nexo Edge 0.2.0 with Operator 008260c and Proxy 7064b41; later behavior must not be inferred.
- The 0.2.0 router phase is configuration-only and does not execute route selection.
Inspect with kubectl
kubectl get nexorouters --namespace <namespace>
kubectl describe nexorouters <name> --namespace <namespace>
kubectl get nexorouters <name> --namespace <namespace> -o yaml
kubectl get crd nexorouters.nexo.io -o yaml
For resources participating in a Proxy graph, also inspect:
kubectl get nexoproxy <proxy-name> --namespace <namespace> \
-o jsonpath='{.status.phase}{" graph="}{.status.graphRevision}{" applied="}{.status.appliedRevision}{"\n"}'
kubectl get nexopipeline <pipeline-name> --namespace <namespace> -o yaml