README

Crate Operator

crate-operator turns a namespaced Crate custom resource into a CrateDB StatefulSet and two Services. Kubernetes creates the pods and persistent volume claims from the StatefulSet.

Audience Guide Topics
Application teams User guide Requests, configuration, connections, inspection, deletion
Cluster administrators Administrator guide Installation, RBAC, storage, maintenance, recovery, removal

Current behavior

  • API group/version: k8s.tlspu.com/v1; kind: Crate; plural: crates.
  • Requests and their generated resources live in the same namespace. One controller watches all namespaces.
  • Only creation and deletion events are handled. Changing a request's spec does not scale, upgrade, or resize the database.
  • The operator has no health status, backup, restore, authentication, or TLS management. Its spec.created flag records that a request was processed, even when provisioning failed.

These guides follow the checked-in controller and CRD. The deployment template and test fixture use the legacy crate-operator.limbicly.com group. Use the corrected examples in these guides.