ParadeDB Community can run on Kubernetes as a single-node deployment. Use
ParadeDB Enterprise when ParadeDB indexes need
physical replication for high
availability, failover, or
read replicas that can serve ParadeDB queries.
Prerequisites
This guide assumes you have installed Helm and have a Kubernetes cluster running v1.29+. For local testing, we recommend Minikube.Install the Prometheus Stack
The ParadeDB Helm chart supports monitoring via Prometheus and Grafana. To enable this, you need to have the Prometheus CRDs installed before installing the CloudNativePG operator. If you do not yet have the Prometheus CRDs installed on your Kubernetes cluster, you can install them with:Install the CloudNativePG Operator
Skip this step if the CloudNativePG operator is already installed in your cluster. If you do not wish to monitor your cluster, omit the--set commands.
Start a ParadeDB CNPG Cluster
Create avalues.yaml and configure it to your requirements. Here is a basic example:
If you are using ParadeDB Enterprise for high availability, set
instances to
a number greater than 1.ParadeDB Enterprise
Use the Extension Image with CloudNativePG
If you already run a CloudNativePG cluster and want to add ParadeDB to an existing Postgres image, use the ParadeDB extension image instead of the fullparadedb/paradedb image. Extension images require Postgres 18+ because they
depend on extension_control_path.
Add the pg_search extension image to the postgresql.extensions section of
your CloudNativePG Cluster resource:
<paradedb-version>-<postgres-major>-trixie.
For example, use {version}-18-trixie for ParadeDB {version} on Postgres 18.
Connect to the Cluster
The command to connect to the primary instance of the cluster will be printed in your terminal. If you do not modify any settings, it will be:psql with:
Connect to the Grafana Dashboard
To connect to the Grafana dashboard for your cluster, we suggested port forwarding the Kubernetes service running Grafana to localhost:localhost:3000 using admin as the username
and prom-operator as the password. These default credentials are defined in the kube-stack-config.yaml
file used as the values.yaml file in Install the Prometheus Stack and can be modified by providing
your own values.yaml file. A more detailed guide on monitoring the cluster can be found in the CloudNativePG documentation.