Configuring Database Settings for CloudPrem 2 Helm Installation

Last updated: July 16, 2025

This guide explains how to properly configure database (PostgreSQL) settings when installing CloudPrem 2 using Helm, particularly for Dex and Membership services.

Important Prerequisites

Before proceeding with the configuration:

  • Ensure you are using a compatible version of the CloudPrem Helm chart

  • Note that Dex is not compatible with IAM authentication

Database Configuration Steps

1. PostgreSQL Authentication

There are two ways to configure PostgreSQL authentication:

Using Existing Secrets

If you have existing database credentials stored as Kubernetes secrets:

  • Set the secret name using .Values.global.postgresql.auth.existingSecret

  • Mount the secret in .Values.membership.dex.envVars

  • Ensure the secret key matches the key specified in the Dex configuration

Direct Configuration

You can configure PostgreSQL access directly in your values file using the following paths:

  • For Membership service: .Values.membership.postgresql

  • For Dex configuration overrides: .Values.membership.dex.configOverrides

Additional Configuration

If you need to configure additional PostgreSQL users for database migrations, use the migration configuration settings under .Values.membership.migrations.

Troubleshooting Tip: If you encounter authentication errors in the logs, double-check that:

  • All database credentials are correctly specified in your values file

  • The secret names and keys match exactly between your configuration and Kubernetes secrets

  • The database is accessible from your Kubernetes cluster

For detailed configuration examples and reference, consult our Helm charts repository.