NexoQueryGuard
:::danger Schema only — no 0.2.0 reconciliation or enforcement
The 0.2.0 chart installs this schema, but pinned Operator 008260c does not register or reconcile the Kind. Creating the object cannot enforce policy.
:::
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 | NexoQueryGuard |
| API group | nexo.io |
| Version | v1alpha1 |
| Resource | nexoqueryguards |
| Short name | nqg |
| Scope | Namespaced |
| Operator support | Schema only — no 0.2.0 reconciliation or enforcement |
Purpose and relationships
Declares query and command policy.
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.
The CRD schema declares an object but no configurable fields.
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.configHash | string | 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.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. |
Although the schema may expose status fields, the pinned Operator does not populate them.
Reconciliation and watch behavior
Pinned Operator 008260c has no type registration or controller for this Kind. No status controller runs and no NexoProxy graph resolver can consume it as a typed component.
There is no watch for this Kind in the pinned Operator.
Runtime execution effect
None in 0.2.0. The pinned Operator cannot consume the object, so the installed schema has no data-path effect.
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: NexoQueryGuard
metadata:
name: <inspection-only-name>
namespace: <namespace>
spec: {}
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 schema exposes no spec fields, so an accepted empty object does not configure useful policy.
Inspect with kubectl
kubectl get nexoqueryguards --namespace <namespace>
kubectl describe nexoqueryguards <name> --namespace <namespace>
kubectl get nexoqueryguards <name> --namespace <namespace> -o yaml
kubectl get crd nexoqueryguards.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