charts

ParadeDB Helm Chart

Trigger test, remove once done.

The ParadeDB Helm Chart is based on the official CloudNativePG Helm Chart. CloudNativePG is a Kubernetes operator that manages the full lifecycle of a highly available PostgreSQL database cluster with a primary/standby architecture using Postgres streaming (physical) replication.

Kubernetes, and specifically the CloudNativePG operator, is the recommended approach for deploying ParadeDB in production, with high availability. ParadeDB also provides a Docker image and prebuilt binaries for Debian, Ubuntu, Red Hat Enterprise Linux, and macOS.

The ParadeDB Helm Chart supports Postgres 14+ and ships with Postgres 17 by default.

The chart is also available on Artifact Hub.

Usage

ParadeDB Bring-Your-Own-Cloud (BYOC)

The most reliable way to run ParadeDB in production is with ParadeDB BYOC, an end-to-end managed solution that runs in the customer’s cloud account. It deploys on managed Kubernetes services and uses the ParadeDB Helm Chart.

ParadeDB BYOC includes built-in integration with managed PostgreSQL services, such as AWS RDS and GCP CloudSQL, via logical replication. It also provides monitoring, logging and alerting through Prometheus and Grafana. The ParadeDB team manages the underlying infrastructure and lifecycle of the cluster.

You can read more about the optimal architecture for running ParadeDB in production here and you can contact sales here.

Self-Hosted

First, install Helm. The following steps assume you have a Kubernetes cluster running v1.29+. If you are testing locally, we recommend using Minikube.

Monitoring

The ParadeDB Helm chart supports monitoring via Prometheus and Grafana. To enable monitoring, you need to have the Prometheus CRDs installed before installing the CloudNativePG operator. The Promotheus CRDs can be found here.

Installing the CloudNativePG Operator

Skip this step if the CloudNativePG operator is already installed in your cluster. For advanced CloudNativePG configuration and monitoring, please refer to the CloudNativePG Cluster Chart documentation.

helm repo add cnpg https://cloudnative-pg.github.io/charts
helm upgrade --atomic --install cnpg \
--create-namespace \
--namespace cnpg-system \
cnpg/cloudnative-pg

Setting up a ParadeDB CNPG Cluster

[!IMPORTANT] When deploying a cluster with more than one instance, you must use type: paradedb-enterprise to enable replication of BM25 indexes across instances. Using ParadeDB Enterprise requires an access token. To request one, please contact sales.

Create a values.yaml and configure it to your requirements. Here is a basic example:

type: paradedb
mode: standalone

cluster:
  instances: 1
  storage:
    size: 256Mi

Then, launch the ParadeDB cluster.

helm repo add paradedb https://paradedb.github.io/charts
helm upgrade --atomic --install paradedb \
--namespace paradedb \
--create-namespace \
--values values.yaml \
paradedb/paradedb

If --values values.yaml is omitted, the default values will be used. For advanced ParadeDB configuration and monitoring, please refer to the ParadeDB Chart documentation.

Connecting to a ParadeDB CNPG Cluster

You can launch a Bash shell inside a specific pod via:

kubectl exec --stdin --tty <pod-name> -n paradedb -- bash

The primary is called paradedb-1. The replicas are called paradedb-2 onwards depending on the number of replicas you configured. You can connect to the ParadeDB database with psql via:

psql -d paradedb

Development

To test changes to the Chart on a local Minikube cluster, follow the instructions from Self Hosted replacing the helm upgrade step by the path to the directory of the modified Chart.yaml.

helm upgrade --atomic --install paradedb --namespace paradedb --create-namespace ./charts/paradedb

Advanced Cluster Configuration

Database Types

To create a ParadeDB cluster, you must specify either paradedb or paradedb-enterprise via the type parameter.

[!IMPORTANT] When using paradedb-enterprise you must also specify the cluster.imagePullSecrets containing the Docker registry credentials. You can create one with:

kubectl -n NAMESPACE create secret docker-registry paradedb-enterprise-registry-cred --docker-server="https://index.docker.io/v1/" --docker-username="USERNAME" --docker-password="ACCESS_TOKEN"

You then need to set the name of the secret in the values.yaml file with:

type: paradedb-enterprise
cluster:
  imagePullSecrets:
   - name: paradedb-enterprise-registry-cred

Modes of Operation

The chart has three modes of operation. These are configured via the mode parameter:

Backup Configuration

CNPG implements disaster recovery via Barman. The following section configures the barman object store where backups will be stored. Barman performs backups of the cluster filesystem base backup and WALs. Both are stored in the specified location. The backup provider is configured via the backups.provider parameter. The following providers are supported:

Additionally you can specify the following parameters:

backups:
  scheduledBackups:
    - name: daily-backup
      schedule: "0 0 0 * * *" # Daily at midnight
      backupOwnerReference: self

Each backup adapter takes it’s own set of parameters, listed in the Configuration options section below. Refer to the table for the full list of parameters and place the configuration under the appropriate key: backup.s3, backup.azure, or backup.google.

Recovery

There is a separate document outlining the recovery procedure here: Recovery

Monitoring

The ParadeDB Helm chart supports monitoring with Prometheus and Grafana. The chart includes a comprehensive Grafana dashboard that provides complete monitoring for both PostgreSQL/cluster operations and ParadeDB-specific search and analytics features. The dashboard is provisioned as a ConfigMap that works with the Grafana sidecar to automatically import dashboards. You can enable this by setting monitoring.grafanaDashboard.create.

Note: This is a complete, all-in-one dashboard that includes both standard CloudNativePG monitoring (replication, backups, storage, WAL, connections) and ParadeDB-specific metrics (BM25 indexes, index segments). You do not need to install any additional dashboards.

Dashboard Features

The comprehensive dashboard includes monitoring for:

PostgreSQL & Cluster Management:

ParadeDB Search & Analytics:

Alternatively, you can manually import the dashboard from the monitoring directory.

Metrics Configuration

Additionally, we recommend enabling the kube-state-metrics CRD monitoring and adding the CNPG metrics. The configuration can be found in monitoring/metrics-clusters_postgresql_cnpg_io.yaml.

Examples

There are several configuration examples in the examples directory. Refer to them for a basic setup and refer to the CloudNativePG Documentation for more advanced configurations.

Values

Key Type Default Description
backups.azure.connectionString string ""  
backups.azure.containerName string ""  
backups.azure.inheritFromAzureAD bool false  
backups.azure.path string "/"  
backups.azure.serviceName string "blob"  
backups.azure.storageAccount string ""  
backups.azure.storageKey string ""  
backups.azure.storageSasToken string ""  
backups.data.compression string "gzip" Data compression method. One of `` (for no compression), gzip, bzip2 or snappy.
backups.data.encryption string "AES256" Whether to instruct the storage provider to encrypt data files. One of `` (use the storage container default), AES256 or aws:kms.
backups.data.jobs int 2 Number of data files to be archived or restored in parallel.
backups.destinationPath string "" Overrides the provider specific default path. Defaults to: S3: s3:// Azure: https://..core.windows.net/ Google: gs://
backups.enabled bool false You need to configure backups manually, so backups are disabled by default.
backups.endpointCA object {"create":false,"key":"","name":"","value":""} Specifies a CA bundle to validate a privately signed certificate.
backups.endpointCA.create bool false Creates a secret with the given value if true, otherwise uses an existing secret.
backups.endpointURL string "" Overrides the provider specific default endpoint. Defaults to: S3: https://s3..amazonaws.com"
backups.google.applicationCredentials string ""  
backups.google.bucket string ""  
backups.google.gkeEnvironment bool false  
backups.google.path string "/"  
backups.provider string "s3" One of s3, azure or google
backups.retentionPolicy string "30d" Retention policy for backups
backups.s3.accessKey string ""  
backups.s3.bucket string ""  
backups.s3.inheritFromIAMRole bool false Use the role based authentication without providing explicitly the keys
backups.s3.path string "/"  
backups.s3.region string ""  
backups.s3.secretKey string ""  
backups.scheduledBackups[0].backupOwnerReference string "self" Backup owner reference
backups.scheduledBackups[0].method string "barmanObjectStore" Backup method, can be barmanObjectStore (default) or volumeSnapshot
backups.scheduledBackups[0].name string "daily-backup" Scheduled backup name
backups.scheduledBackups[0].schedule string "0 0 0 * * *" Schedule in cron format
backups.secret.create bool true Whether to create a secret for the backup credentials
backups.secret.name string "" Name of the backup credentials secret
backups.wal.compression string "gzip" WAL compression method. One of `` (for no compression), gzip, bzip2 or snappy.
backups.wal.encryption string "AES256" Whether to instruct the storage provider to encrypt WAL files. One of `` (use the storage container default), AES256 or aws:kms.
backups.wal.maxParallel int 1 Number of WAL files to be archived or restored in parallel.
cluster.additionalLabels object {}  
cluster.affinity object {"topologyKey":"topology.kubernetes.io/zone"} Affinity/Anti-affinity rules for Pods. See: https://cloudnative-pg.io/documentation/current/cloudnative-pg.v1/#postgresql-cnpg-io-v1-AffinityConfiguration
cluster.annotations object {}  
cluster.certificates object {} The configuration for the CA and related certificates. See: https://cloudnative-pg.io/documentation/current/cloudnative-pg.v1/#postgresql-cnpg-io-v1-CertificatesConfiguration
cluster.console.enabled bool false Deploys a console StatefulSet to run long-running commands against the cluster (e.g. CREATE INDEX).
cluster.enablePDB bool true Allow to disable PDB, mainly useful for upgrade of single-instance clusters or development purposes See: https://cloudnative-pg.io/documentation/current/kubernetes_upgrade/#pod-disruption-budgets
cluster.enableSuperuserAccess bool true When this option is enabled, the operator will use the SuperuserSecret to update the postgres user password. If the secret is not present, the operator will automatically create one. When this option is disabled, the operator will ignore the SuperuserSecret content, delete it when automatically created, and then blank the password of the postgres user by setting it to NULL.
cluster.env list [] Env follows the Env format to pass environment variables to the pods created in the cluster
cluster.envFrom list [] EnvFrom follows the EnvFrom format to pass environment variables sources to the pods to be used by Env
cluster.imageCatalogRef object {} Reference to ImageCatalog of ClusterImageCatalog, if specified takes precedence over cluster.imageName
cluster.imageName string "" Name of the container image, supporting both tags (:) and digests for deterministic and repeatable deployments: :@sha256:
cluster.imagePullPolicy string "IfNotPresent" Image pull policy. One of Always, Never or IfNotPresent. If not defined, it defaults to IfNotPresent. Cannot be updated. More info: https://kubernetes.io/docs/concepts/containers/images#updating-images
cluster.imagePullSecrets list [] The list of pull secrets to be used to pull the images. See: https://cloudnative-pg.io/documentation/current/cloudnative-pg.v1/#postgresql-cnpg-io-v1-LocalObjectReference
cluster.initdb object {"database":"paradedb"} BootstrapInitDB is the configuration of the bootstrap process when initdb is used. See: https://cloudnative-pg.io/documentation/current/bootstrap/ See: https://cloudnative-pg.io/documentation/current/cloudnative-pg.v1/#postgresql-cnpg-io-v1-bootstrapinitdb
cluster.instances int 3 Number of instances
cluster.logLevel string "info" The instances’ log level, one of the following values: error, warning, info (default), debug, trace
cluster.monitoring.customQueries list [] Custom Prometheus metrics Will be stored in the ConfigMap
cluster.monitoring.customQueriesSecret list [] The list of secrets containing the custom queries
cluster.monitoring.disableDefaultQueries bool false Whether the default queries should be injected. Set it to true if you don’t want to inject default queries into the cluster.
cluster.monitoring.enabled bool false Whether to enable monitoring
cluster.monitoring.instrumentation.logicalReplication bool false Enable logical replication metrics
cluster.monitoring.instrumentation.paradedbIndex bool true Enable ParadeDB index metrics
cluster.monitoring.podMonitor.enabled bool true Whether to enable the PodMonitor
cluster.monitoring.podMonitor.metricRelabelings list [] The list of metric relabelings for the PodMonitor. Applied to samples before ingestion.
cluster.monitoring.podMonitor.relabelings list [] The list of relabelings for the PodMonitor. Applied to samples before scraping.
cluster.monitoring.prometheusRule.enabled bool true Whether to enable the PrometheusRule automated alerts
cluster.monitoring.prometheusRule.excludeRules list [] Exclude specified rules
cluster.postgresGID int -1 The GID of the postgres user inside the image, defaults to 26
cluster.postgresUID int -1 The UID of the postgres user inside the image, defaults to 26
cluster.postgresql.ldap object {} PostgreSQL LDAP configuration (see https://cloudnative-pg.io/documentation/current/postgresql_conf/#ldap-configuration)
cluster.postgresql.parameters object {"cron.database_name":"postgres"} PostgreSQL configuration options (postgresql.conf)
cluster.postgresql.pg_hba list [] PostgreSQL Host Based Authentication rules (lines to be appended to the pg_hba.conf file)
cluster.postgresql.pg_ident list [] PostgreSQL User Name Maps rules (lines to be appended to the pg_ident.conf file)
cluster.postgresql.shared_preload_libraries list [] Lists of shared preload libraries to add to the default ones
cluster.postgresql.synchronous object {} Quorum-based Synchronous Replication
cluster.primaryUpdateMethod string "switchover" Method to follow to upgrade the primary server during a rolling update procedure, after all replicas have been successfully updated. It can be switchover (default) or restart.
cluster.primaryUpdateStrategy string "unsupervised" Strategy to follow to upgrade the primary server during a rolling update procedure, after all replicas have been successfully updated: it can be automated (unsupervised - default) or manual (supervised)
cluster.priorityClassName string ""  
cluster.resources object {} Resources requirements of every generated Pod. Please refer to https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ for more information. We strongly advise you use the same setting for limits and requests so that your cluster pods are given a Guaranteed QoS. See: https://kubernetes.io/docs/concepts/workloads/pods/pod-qos/
cluster.roles list [] This feature enables declarative management of existing roles, as well as the creation of new roles if they are not already present in the database. See: https://cloudnative-pg.io/documentation/current/declarative_role_management/
cluster.serviceAccountTemplate object {} Configure the metadata of the generated service account
cluster.services object {} Customization of service definitions. Please refer to https://cloudnative-pg.io/documentation/current/service_management/
cluster.storage.size string "8Gi"  
cluster.storage.storageClass string ""  
cluster.superuserSecret string ""  
cluster.walStorage.enabled bool false  
cluster.walStorage.size string "1Gi"  
cluster.walStorage.storageClass string ""  
databases list []  
fullnameOverride string "" Override the full name of the chart
imageCatalog.create bool true Whether to provision an image catalog. If imageCatalog.images is empty this option will be ignored.
imageCatalog.images list [] List of images to be provisioned in an image catalog.
mode string "standalone" Cluster mode of operation. Available modes: * standalone - default mode. Creates new or updates an existing CNPG cluster. * replica - Creates a replica cluster from an existing CNPG cluster. * recovery - Same as standalone but creates a cluster from a backup, object store or via pg_basebackup.
monitoring.grafanaDashboard.annotations object {} Annotations that ConfigMaps can have to get configured in Grafana.
monitoring.grafanaDashboard.configMapName string "paradedb-grafana-dashboard" The name of the ConfigMap containing the dashboard.
monitoring.grafanaDashboard.create bool true  
monitoring.grafanaDashboard.labels object {"grafana_dashboard":"1"} Labels that ConfigMaps should have to get configured in Grafana.
monitoring.grafanaDashboard.namespace string "monitoring" Allows overriding the namespace where the ConfigMap will be created, defaulting to the same one as the Release.
nameOverride string "" Override the name of the chart
namespaceOverride string "" Override the namespace of the chart
poolers list [] List of PgBouncer poolers
recovery.azure.connectionString string ""  
recovery.azure.containerName string ""  
recovery.azure.inheritFromAzureAD bool false  
recovery.azure.path string "/"  
recovery.azure.serviceName string "blob"  
recovery.azure.storageAccount string ""  
recovery.azure.storageKey string ""  
recovery.azure.storageSasToken string ""  
recovery.backupName string "" Backup Recovery Method
recovery.clusterName string "" The original cluster name when used in backups. Also known as serverName.
recovery.database string "paradedb" Name of the database used by the application. Default: paradedb.
recovery.destinationPath string "" Overrides the provider specific default path. Defaults to: S3: s3:// Azure: https://..core.windows.net/ Google: gs://
recovery.endpointCA object {"create":false,"key":"","name":"","value":""} Specifies a CA bundle to validate a privately signed certificate.
recovery.endpointCA.create bool false Creates a secret with the given value if true, otherwise uses an existing secret.
recovery.endpointURL string "" Overrides the provider specific default endpoint. Defaults to: S3: https://s3..amazonaws.com" Leave empty if using the default S3 endpoint
recovery.google.applicationCredentials string ""  
recovery.google.bucket string ""  
recovery.google.gkeEnvironment bool false  
recovery.google.path string "/"  
recovery.import.databases list [] Databases to import
recovery.import.pgDumpExtraOptions list [] List of custom options to pass to the pg_dump command. IMPORTANT: Use these options with caution and at your own risk, as the operator does not validate their content. Be aware that certain options may conflict with the operator’s intended functionality or design.
recovery.import.pgRestoreExtraOptions list [] List of custom options to pass to the pg_restore command. IMPORTANT: Use these options with caution and at your own risk, as the operator does not validate their content. Be aware that certain options may conflict with the operator’s intended functionality or design.
recovery.import.postImportApplicationSQL list [] List of SQL queries to be executed as a superuser in the application database right after is imported. To be used with extreme care. Only available in microservice type.
recovery.import.roles list [] Roles to import
recovery.import.schemaOnly bool false When set to true, only the pre-data and post-data sections of pg_restore are invoked, avoiding data import.
recovery.import.source.database string "paradedb"  
recovery.import.source.host string ""  
recovery.import.source.passwordSecret.create bool false Whether to create a secret for the password
recovery.import.source.passwordSecret.key string "password" The key in the secret containing the password
recovery.import.source.passwordSecret.name string "" Name of the secret containing the password
recovery.import.source.passwordSecret.value string "" The password value to use when creating the secret
recovery.import.source.port int 5432  
recovery.import.source.sslCertSecret.key string ""  
recovery.import.source.sslCertSecret.name string ""  
recovery.import.source.sslKeySecret.key string ""  
recovery.import.source.sslKeySecret.name string ""  
recovery.import.source.sslMode string "verify-full"  
recovery.import.source.sslRootCertSecret.key string ""  
recovery.import.source.sslRootCertSecret.name string ""  
recovery.import.source.username string ""  
recovery.import.type string "microservice" One of microservice or monolith. See: https://cloudnative-pg.io/documentation/current/database_import/#how-it-works
recovery.method string "backup" Available recovery methods: * backup - Recovers a CNPG cluster from a CNPG backup (PITR supported) Needs to be on the same cluster in the same namespace. * object_store - Recovers a CNPG cluster from a barman object store (PITR supported). * pg_basebackup - Recovers a CNPG cluster viaa streaming replication protocol. Useful if you want to migrate databases to CloudNativePG, even from outside Kubernetes. * import - Import one or more databases from an existing Postgres cluster.
recovery.owner string "" Name of the owner of the database in the instance to be used by applications. Defaults to the value of the database key.
recovery.pgBaseBackup.database string "paradedb" Name of the database used by the application. Default: paradedb.
recovery.pgBaseBackup.owner string "" Name of the owner of the database in the instance to be used by applications. Defaults to the value of the database key.
recovery.pgBaseBackup.secret string "" Name of the secret containing the initial credentials for the owner of the user database. If empty a new secret will be created from scratch
recovery.pgBaseBackup.source.database string "paradedb"  
recovery.pgBaseBackup.source.host string ""  
recovery.pgBaseBackup.source.passwordSecret.create bool false Whether to create a secret for the password
recovery.pgBaseBackup.source.passwordSecret.key string "password" The key in the secret containing the password
recovery.pgBaseBackup.source.passwordSecret.name string "" Name of the secret containing the password
recovery.pgBaseBackup.source.passwordSecret.value string "" The password value to use when creating the secret
recovery.pgBaseBackup.source.port int 5432  
recovery.pgBaseBackup.source.sslCertSecret.key string ""  
recovery.pgBaseBackup.source.sslCertSecret.name string ""  
recovery.pgBaseBackup.source.sslKeySecret.key string ""  
recovery.pgBaseBackup.source.sslKeySecret.name string ""  
recovery.pgBaseBackup.source.sslMode string "verify-full"  
recovery.pgBaseBackup.source.sslRootCertSecret.key string ""  
recovery.pgBaseBackup.source.sslRootCertSecret.name string ""  
recovery.pgBaseBackup.source.username string ""  
recovery.pitrTarget.time string "" Time in RFC3339 format
recovery.provider string "s3" One of s3, azure or google
recovery.s3.accessKey string ""  
recovery.s3.bucket string ""  
recovery.s3.inheritFromIAMRole bool false Use the role based authentication without providing explicitly the keys
recovery.s3.path string "/"  
recovery.s3.region string ""  
recovery.s3.secretKey string ""  
recovery.secret.create bool true Whether to create a secret for the backup credentials
recovery.secret.name string "" Name of the backup credentials secret
replica.bootstrap.database string "" Name of the database used by the application
replica.bootstrap.owner string "" Name of the owner of the database in the instance to be used by applications. Defaults to the value of the database key.
replica.bootstrap.secret string "" Name of the secret containing the initial credentials for the owner of the user database. If empty a new secret will be created from scratch
replica.bootstrap.source string "" One of object_store or pg_basebackup. Method to use for bootstrap.
replica.minApplyDelay string "" When replica mode is enabled, this parameter allows you to replay transactions only when the system time is at least the configured time past the commit time. This provides an opportunity to correct data loss errors. Note that when this parameter is set, a promotion token cannot be used.
replica.origin.objectStore.azure.connectionString string ""  
replica.origin.objectStore.azure.containerName string ""  
replica.origin.objectStore.azure.inheritFromAzureAD bool false  
replica.origin.objectStore.azure.path string "/"  
replica.origin.objectStore.azure.serviceName string "blob"  
replica.origin.objectStore.azure.storageAccount string ""  
replica.origin.objectStore.azure.storageKey string ""  
replica.origin.objectStore.azure.storageSasToken string ""  
replica.origin.objectStore.clusterName string "" The original cluster name when used in backups. Also known as serverName.
replica.origin.objectStore.destinationPath string "" Overrides the provider specific default path. Defaults to: S3: s3:// Azure: https://..core.windows.net/ Google: gs://
replica.origin.objectStore.endpointCA object {"create":false,"key":"","name":"","value":""} Specifies a CA bundle to validate a privately signed certificate.
replica.origin.objectStore.endpointCA.create bool false Creates a secret with the given value if true, otherwise uses an existing secret.
replica.origin.objectStore.google.applicationCredentials string ""  
replica.origin.objectStore.google.bucket string ""  
replica.origin.objectStore.google.gkeEnvironment bool false  
replica.origin.objectStore.google.path string "/"  
replica.origin.objectStore.provider string "" One of s3, azure or google
replica.origin.objectStore.s3.accessKey string ""  
replica.origin.objectStore.s3.bucket string ""  
replica.origin.objectStore.s3.inheritFromIAMRole bool false Use the role based authentication without providing explicitly the keys
replica.origin.objectStore.s3.path string "/"  
replica.origin.objectStore.s3.region string ""  
replica.origin.objectStore.s3.secretKey string ""  
replica.origin.objectStore.secret.create bool true Whether to create a secret for the backup credentials
replica.origin.objectStore.secret.name string "" Name of the backup credentials secret
replica.origin.pg_basebackup.database string ""  
replica.origin.pg_basebackup.host string ""  
replica.origin.pg_basebackup.passwordSecret.key string ""  
replica.origin.pg_basebackup.passwordSecret.name string ""  
replica.origin.pg_basebackup.port int 5432  
replica.origin.pg_basebackup.sslCertSecret.key string ""  
replica.origin.pg_basebackup.sslCertSecret.name string ""  
replica.origin.pg_basebackup.sslKeySecret.key string ""  
replica.origin.pg_basebackup.sslKeySecret.name string ""  
replica.origin.pg_basebackup.sslMode string "verify-full"  
replica.origin.pg_basebackup.sslRootCertSecret.key string ""  
replica.origin.pg_basebackup.sslRootCertSecret.name string ""  
replica.origin.pg_basebackup.username string ""  
replica.primary string "" Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the topology specified in externalClusters
replica.promotionToken string "" A demotion token generated by an external cluster used to check if the promotion requirements are met.
replica.self string "" Defines the name of this cluster. It is used to determine if this is a primary or a replica cluster, comparing it with primary. Leave empty by default.
type string "paradedb" Type of the CNPG database. Available types: * paradedb * paradedb-enterprise
version.paradedb string "0.19.5" We default to v0.19.5 for testing and local development
version.postgresql string "17" PostgreSQL major version to use
poolers[].name string `` Name of the pooler resource
poolers[].instances number 1 The number of replicas we want
poolers[].type [PoolerType][PoolerType] rw Type of service to forward traffic to. Default: rw.
poolers[].poolMode [PgBouncerPoolMode][PgBouncerPoolMode] session The pool mode. Default: session.
poolers[].authQuerySecret [LocalObjectReference][LocalObjectReference] {} The credentials of the user that need to be used for the authentication query.
poolers[].authQuery string {} The credentials of the user that need to be used for the authentication query.
poolers[].parameters map[string]string {} Additional parameters to be passed to PgBouncer - please check the CNPG documentation for a list of options you can configure
poolers[].template [PodTemplateSpec][PodTemplateSpec] {} The template of the Pod to be created
poolers[].template [ServiceTemplateSpec][ServiceTemplateSpec] {} Template for the Service to be created
poolers[].pg_hba []string {} PostgreSQL Host Based Authentication rules (lines to be appended to the pg_hba.conf file)
poolers[].monitoring.enabled bool false Whether to enable monitoring for the Pooler.
poolers[].monitoring.podMonitor.enabled bool true Create a podMonitor for the Pooler.

Maintainers

Name Email Url
ParadeDB support@paradedb.com https://paradedb.com

License

ParadeDB is licensed under the GNU Affero General Public License v3.0 and as commercial software. For commercial licensing, please contact us at sales@paradedb.com.