cue-kind-definition

To define a grafana-app-sdk CUE kind, you structure three CUE layers: common kind metadata, per-version schema, and app manifest registration. You separate user-desired state into spec and operator-observed fields into status to match the Kubernetes-style resource model.

The correct CUE anatomy for generating Kubernetes CRDs involves three layers: common kind metadata, per-version schemas with validation constraints, and app manifest registration. This structure ensures generated clients, types, and manifests align with your intended resource model.

To add a new version to a CUE kind definition without breaking API compatibility, you configure a new per-version schema alongside existing ones and apply version compatibility rules. This allows safe schema extension while maintaining valid code generation for all targets.

Yes, you can toggle TypeScript and Go code generation independently in CUE kind definitions. By setting per-version codegen toggles within your schema design, you control exactly which target clients and types are generated for each API version.

Your generated CRD manifest may not match your intended model if the CUE kind definition lacks proper spec and status separation or validation constraints. Enforce Kubernetes-style conventions and ensure the three-layer CUE anatomy is correctly structured.