Operator configuration validation

The pinned 0.2.0 Operator validates registered custom-resource fields, references, managed signatures, and resource readiness while resolving the desired graph.

:::warning No rendered-runtime schema gate

0.2.0 does not validate rendered component configuration against the later nexo-step-contract/configschema registry before writing ConfigMaps or workload changes. Do not rely on that post-0.2.0 control.

:::

0.2.0 validation sequence

1. Resolve the NexoProxy, pipeline, deployment profile, and registered component references.
2. Apply the type-specific validation compiled into the pinned Operator.
3. Require referenced resources to be ready where the registered reconciler implements that requirement.
4. Report reconciliation errors through resource status and Kubernetes events.
5. Render the workload only for a graph accepted by those 0.2.0 checks.

Installing a CRD schema does not mean its kind is registered or reconciled. See the CRD catalog for the exact support matrix.

Safe rollout

• Validate representative configuration in an isolated environment.
• Inspect resource conditions and events after every change.
• Confirm the active graph revision before routing traffic.
• Preserve a known-good configuration for rollback.