QuestDB Enterprise Kubernetes Operator
The Kubernetes Operator manages QuestDB Enterprise clusters. For open source QuestDB on Kubernetes, use the QuestDB Helm chart.
:::warning[Supported platforms] The API is questdb.io/v1alpha1 and may change between
releases. Amazon EKS and Azure AKS are supported on the tested versions in the support matrix.
See Support for support expectations.
:::
The QuestDB Enterprise Operator manages the Kubernetes lifecycle of QuestDB Enterprise: database pods and storage, configuration, engine-driven backup, replication and promotion, restore and point-in-time recovery, and health status.
You bring an existing object store. The operator has no cloud IAM or identity and performs no object-store I/O: it never creates, reads, or deletes buckets or containers. With static authentication, it reads the referenced Kubernetes Secret only to inject database pod configuration; ambient EKS IRSA avoids that static Secret. QuestDB database pods perform all object-store I/O.
Choose your path
- Amazon EKS: follow the EKS onboarding guide.
- Azure AKS: follow the AKS onboarding guide.
- Shared install requirements: see Installation.
- Restore or migrate existing data: follow the cloud-neutral restore and migration guide.
- PGWire TLS and network isolation: plan them before creation with Configuration.
- Operate the operator: use the operator runbook.
- Operate a database: use the database, backup and restore, or high-availability runbook.
- Diagnose a problem: use Troubleshooting.
Use Configuration for common resource shapes and the API Reference for every field, default, and validation rule.