DataResource Custom Resources
A single Kubernetes CRD abstraction provisions and lifecycle-manages storage, databases, search, streaming, and analytics engines.
- One `DataResource` custom resource covers 17 documented types — `pvc/block`, `pvc/file`, `object`, `nfs`, `iscsi`, `postgres`, `keyvalue`, `search`, `kafka`, `clickhouse`, `warehouse/trino`, `lakehouse/iceberg`, `timeseries`, `vector`, `mariadb`, `mysql`, and `ferretdb`.
- The k8s-controller watches every DataResource and reconciles it against the matching upstream operator (CloudNativePG, Valkey Operator, OpenSearch Operator, Strimzi, or a cloud SDK for external mode).
- Status is reflected back onto `status.phase`, `status.conditions`, and `status.endpoints` so consumers can watch readiness the same way for every type.
- Three origination modes — managed, external, and imported — are selected per-resource via `spec.origination`.