Home Why Orkestra Reference SchemaSchemaSchema Reference Document Covers katalog.md Top-level Katalog structure crd-entry.md Fields inside spec.crds.<name> apitypes.md … apiTypes Declares the Kubernetes API group, kind, and version of the CRD being managed. Every CRDEntry must have apiTypes. … conversion Enables multi-version CRD support via the Orkestra conversion webhook. When declared, Orkestra registers a /convert … CRDEntry Each entry in spec.crds is a CRDEntry. The map key becomes the CRD name at runtime — it is never written in the YAML … notification Configures alerting dispatched when reconciliation errors occur or when a watched condition changes. notification: … providers Declares external provider dependencies — cloud services, databases, or any system Orkestra integrates with via a … security Controls deletion protection, namespace protection, and admission webhooks for the Katalog. security: serviceName: … Katalog A Katalog declares one or more CRDs and defines how Orkestra manages them. It is the unit of operator definition. Wire … Komposer A Komposer is a Katalog with an imports block. The separate kind is intentional — it keeps composition explicit and … Motif A Motif is the smallest reusable unit in Orkestra’s composition model. It declares named inputs and resource … mutation Declarative mutation rules applied at admission time (before creation/update) and optionally at reconcile time. Declared … operatorBox Defines the reconciliation strategy for a CRD. Controls whether Orkestra uses the GenericReconciler with declarative … status Orkestra writes status in two layers — one automatic, one declarative. Layer 1 — automatic (always on). After every … validation Declarative validation rules evaluated at admission time (via webhook) and at reconcile time. Declared on a CRDEntry or … when / anyOf conditions Conditions control whether a resource template field is written during reconciliation. Used inside operatorBox and …