Setting up custom PostgreSQL configuration (Kubernetes)

Edit online

You can custom your PostgreSQL configuration settings, Concert offers the capability to create a ConfigMap for PostgreSQL configuration and mount it as a volume in the PostgreSQL deployment. This optional feature allows you to tailor the external PostgreSQL databases to meet specific requirements. By creating a ConfigMap, you can define custom configuration settings, such as connection limits, memory allocation, and query optimization, which can then be applied to your PostgreSQL databases.

Instructions

Create a new ConfigMap file with filename as configdb-custom or appdb-custom as per your PostgreSQL deployment.
Add the required configuration settings in the following format:
```
setting1: value1
setting2: value2
```
For example:
```
apiVersion: v1
data:
  max_connections: "200"
  shared_buffers: 3280MB
kind: ConfigMap
```
Add each configuration setting on a new line, using the setting: value format.
Save the ConfigMap file with the added configuration settings.
Restart the PostgreSQL deployment:
- Use the following command to restart the configdb deployment.
```
kubectl rollout restart deployment configdb
```
- Use the following command to restart the appdb deployment.
```
kubectl rollout restart deployment appdb
```

Unsupported customizations

The following PostgreSQL configuration settings are not supported:

ssl 
ssl_ca_file 
ssl_cert_file
ssl_key_file 
unix_socket_directories 
archive_mode 
archive_command 
listen_addresses 
shared_preload_libraries
log_directory
pg_auto_failover
port
hot_standby
password_encryption
hba_file