Deploy GreptimeDB on Kubernetes

GreptimeDB runs on Kubernetes, either on-premises or on a cloud provider such as AWS, Alibaba Cloud, or Google Cloud.

Deploy GreptimeDB Standalone

For development, testing, or small-scale production use cases, you can deploy a standalone GreptimeDB instance on Kubernetes, without running a full cluster.

Deploy GreptimeDB Cluster

For production environments requiring high availability and horizontal scaling, deploy a GreptimeDB cluster using the GreptimeDB Operator on Kubernetes.

Configurations

You can apply custom configurations to GreptimeDB by creating a values.yaml file when deploying either GreptimeDB clusters or standalone instances. For a complete list of available configuration options, see Common Helm Chart Configurations.

Manage GreptimeDB Operator

The GreptimeDB Operator automates the setup, provisioning, and management of GreptimeDB instances on Kubernetes. Learn how to manage the GreptimeDB Operator, including installation and upgrades.

Advanced Deployments

Once you are familiar with the architecture and components of GreptimeDB, you can move on to these deployment scenarios:

• Deploy GreptimeDB Infrastructure test: Prerequisite infrastructure testing for installing GreptimeDB.
• Deploy MinIO cluster: Learn how to deploy, configure, and monitor a MinIO cluster.
• Deploy Kafka cluster: Learn how to deploy, configure, and monitor a Kafka cluster.
• Deploy GreptimeDB Cluster with Remote WAL: Configure Kafka as a remote write-ahead log (WAL) for your GreptimeDB cluster, so writes that a Datanode has not yet flushed to storage can be replayed from Kafka after a failure.
• Use MySQL/PostgreSQL as Metadata Store: Store cluster metadata in a MySQL or PostgreSQL database.
• Deploy Multi-Frontend GreptimeDB Cluster: Set up a GreptimeDB cluster on Kubernetes with a frontend group consisting of multiple frontend instances for improved load distribution and availability.