charts/bitnami/postgresql-ha

PostgreSQL HA

This Helm chart has been developed based on bitnami/postgresql chart but including some changes to guarantee high availability such as:

• A new deployment, service and ingress have been added to deploy Pgpool-II to act as proxy for PostgreSQL backend. It helps to reduce connection overhead, acts as a load balancer for PostgreSQL, and ensures database node failover.
• Replacing bitnami/postgresql with bitnami/postgresql-repmgr which includes and configures repmgr. Repmgr ensures standby nodes assume the primary role when the primary node is unhealthy.

TL;DR;

$ helm repo add bitnami https://charts.bitnami.com/bitnami
$ helm install my-release bitnami/postgresql-ha

Introduction

This Helm chart installs PostgreSQL with HA architecture in a Kubernetes cluster. Welcome to contribute to Helm Chart for PostgreSQL HA.

Prerequisites

• Kubernetes 1.12+
• Helm 2.11+ or Helm 3.0-beta3+

Installing the Chart

Install the PostgreSQL HA helm chart with a release name my-release:

$ helm repo add bitnami https://charts.bitnami.com/bitnami
$ helm install my-release bitnami/postgresql-ha

Uninstalling the Chart

To uninstall/delete the my-release deployment:

$ helm delete --purge my-release

Additionaly, if persistence.resourcePolicy is set to keep, you should manually delete the PVCs.

Parameters

The following table lists the configurable parameters of the PostgreSQL HA chart and the default values. They can be configured in values.yaml or set via --set flag during installation.

Parameter	Description	Default
Global
global.imageRegistry	Global Docker image registry	nil
global.imagePullSecrets	Global Docker registry secret names as an array	[] (does not add image pull secrets to deployed pods)
global.storageClass	Global storage class for dynamic provisioning	nil
global.postgresql.existingSecret	Name of existing secret to use for PostgreSQL passwords (overrides postgresql.existingSecret)	nil
global.postgresql.username	PostgreSQL username (overrides postgresql.username)	nil
global.postgresql.password	PostgreSQL password (overrides postgresql.password)	nil
global.postgresql.database	PostgreSQL database (overrides postgresql.database)	nil
global.postgresql.repmgrUsername	PostgreSQL repmgr username (overrides postgresql.repmgrUsername)	nil
global.postgresql.repmgrPassword	PostgreSQL repmgr password (overrides postgresql.repmgrpassword)	nil
global.postgresql.repmgrDatabase	PostgreSQL repmgr database (overrides postgresql.repmgrDatabase)	nil
global.ldap.existingSecret	Name of existing secret to use for LDAP passwords (overrides ldap.existingSecret)	nil
global.ldap.bindpw	LDAP bind password (overrides ldap.bindpw)	nil
global.pgpool.adminUsername	Pgpool Admin username (overrides pgpool.adminUsername)	nil
global.pgpool.adminPassword	Pgpool Admin password (overrides pgpool.adminPassword)	nil
General
nameOverride	String to partially override postgres-ha.fullname template with a string	nil
fullnameOverride	String to fully override postgres-ha.fullname template with a string	nil
clusterDomain	Default Kubernetes cluster domain	cluster.local
PostgreSQL with Repmgr
postgresqlImage.registry	Registry for PostgreSQL with Repmgr image	docker.io
postgresqlImage.repository	Repository for PostgreSQL with Repmgr image	bitnami/postgresql-repmgr
postgresqlImage.tag	Tag for PostgreSQL with Repmgr image	{TAG_NAME}
postgresqlImage.pullPolicy	PostgreSQL with Repmgr image pull policy	IfNotPresent
postgresqlImage.pullSecrets	Specify docker-registry secret names as an array	[] (does not add image pull secrets to deployed pods)
postgresqlImage.debug	Specify if debug logs should be enabled	false
postgresql.labels	Map of labels to add to the statefulset. Evaluated as a template	{}
postgresql.podLabels	Map of labels to add to the pods. Evaluated as a template	{}
postgresql.replicaCount	The number of replicas to deploy	2
postgresql.updateStrategyType	Statefulset update strategy policy	RollingUpdate
postgresql.podAnnotations	Additional pod annotations	{}
postgresql.affinity	Map of node/pod affinities	{} (The value is evaluated as a template)
postgresql.nodeSelector	Node labels for pod assignment	{} (The value is evaluated as a template)
postgresql.priorityClassName	Pod priority class	``
postgresql.tolerations	Tolerations for pod assignment	[] (The value is evaluated as a template)
postgresql.securityContext.enabled	Enable security context for PostgreSQL with Repmgr	true
postgresql.securityContext.fsGroup	Group ID for the PostgreSQL with Repmgr filesystem	1001
postgresql.securityContext.runAsUser	User ID for the PostgreSQL with Repmgr container	1001
postgresql.resources	The [resources] to allocate for container	{}
postgresql.livenessProbe	Liveness probe configuration for PostgreSQL with Repmgr	Check values.yaml file
postgresql.readinessProbe	Readiness probe configuration for PostgreSQL with Repmgr	Check values.yaml file
postgresql.pdb.create	If true, create a pod disruption budget for PostgreSQL with Repmgr pods	false
postgresql.pdb.minAvailable	Minimum number / percentage of pods that should remain scheduled	1
postgresql.pdb.maxUnavailable	Maximum number / percentage of pods that may be made unavailable	nil
postgresql.username	PostgreSQL username	postgres
postgresql.password	PostgreSQL password	nil
postgresql.database	PostgreSQL database	postgres
postgresql.upgradeRepmgrExtension	Upgrade repmgr extension in the database	false
postgresql.pgHbaTrustAll	Configures PostgreSQL HBA to trust every user	false
postgresql.repmgrUsername	PostgreSQL repmgr username	repmgr
postgresql.repmgrPassword	PostgreSQL repmgr password	nil
postgresql.repmgrDatabase	PostgreSQL repmgr database	repmgr
postgresql.repmgrLogLevel	Repmgr log level (DEBUG, INFO, NOTICE, WARNING, ERROR, ALERT, CRIT or EMERG)	NOTICE
postgresql.repmgrConnectTimeout	Repmgr backend connection timeout (in seconds)	5
postgresql.repmgrReconnectAttempts	Repmgr backend reconnection attempts	3
postgresql.repmgrReconnectInterval	Repmgr backend reconnection interval (in seconds)	5
postgresql.repmgrConfiguration	Repmgr Configuration	nil
postgresql.configuration	PostgreSQL Configuration	nil
postgresql.pgHbaConfiguration	Content of pg_hba.conf	nil (do not create pg_hba.conf)
postgresql.configurationCM	ConfigMap with the PostgreSQL configuration files (Note: Overrides postgresql.repmgrConfiguration, postgresql.configuration and postgresql.pgHbaConfiguration)	nil (The value is evaluated as a template)
postgresql.extendedConf	Extended PostgreSQL Configuration (appended to main or default configuration)	nil
postgresql.extendedConfCM	ConfigMap with the extended PostgreSQL configuration files (Note: Overrides postgresql.extendedConf)	nil (The value is evaluated as a template)
postgresql.initdbScripts	Dictionary of initdb scripts	nil
postgresql.initdbScriptsCM	ConfigMap with the initdb scripts (Note: Overrides initdbScripts). The value is evaluated as a template.	nil
postgresql.initdbScriptsSecret	Secret with initdb scripts that contain sensitive information (Note: can be used with initdbScriptsCM or initdbScripts). The value is evaluated as a template.	nil
Pgpool
pgpoolImage.registry	Registry for Pgpool	docker.io
pgpoolImage.repository	Repository for Pgpool	bitnami/pgpool
pgpoolImage.tag	Tag for Pgpool	{TAG_NAME}
pgpoolImage.pullPolicy	Pgpool image pull policy	IfNotPresent
pgpoolImage.pullSecrets	Specify docker-registry secret names as an array	[] (does not add image pull secrets to deployed pods)
pgpoolImage.debug	Specify if debug logs should be enabled	false
pgpool.labels	Map of labels to add to the deployment. Evaluated as a template	{}
pgpool.podLabels	Map of labels to add to the pods. Evaluated as a template	{}
pgpool.replicaCount	The number of replicas to deploy	2
pgpool.podAnnotations	Additional pod annotations	{}
pgpool.affinity	Map of node/pod affinities	{} (The value is evaluated as a template)
pgpool.initdbScripts	Dictionary of initdb scripts	nil
pgpool.initdbScriptsCM	ConfigMap with the initdb scripts (Note: Overrides initdbScripts). The value is evaluated as a template.	nil
pgpool.initdbScriptsSecret	Secret with initdb scripts that contain sensitive information (Note: can be used with initdbScriptsCM or initdbScripts). The value is evaluated as a template.	nil
pgpool.nodeSelector	Node labels for pod assignment	{} (The value is evaluated as a template)
pgpool.priorityClassName	Pod priority class	``
pgpool.tolerations	Tolerations for pod assignment	[] (The value is evaluated as a template)
pgpool.securityContext.enabled	Enable security context for Pgpool	true
pgpool.securityContext.fsGroup	Group ID for the Pgpool filesystem	1001
pgpool.securityContext.runAsUser	User ID for the Pgpool container	1001
pgpool.resources	The [resources] to allocate for container	{}
pgpool.livenessProbe	Liveness probe configuration for Pgpool	Check values.yaml file
pgpool.readinessProbe	Readiness probe configuration for Pgpool	Check values.yaml file
pgpool.pdb.create	If true, create a pod disruption budget for Pgpool pods.	false
pgpool.pdb.minAvailable	Minimum number / percentage of pods that should remain scheduled	1
pgpool.pdb.maxUnavailable	Maximum number / percentage of pods that may be made unavailable	nil
pgpool.adminUsername	Pgpool Admin username	admin
pgpool.adminPassword	Pgpool Admin password	nil
pgpool.maxPool	The maximum number of cached connections in each child process	15
pgpool.numInitChildren	The number of preforked Pgpool-II server processes.	32
pgpool.configuration	Content of pgpool.conf	nil
pgpool.configurationCM	ConfigMap with the Pgpool configuration file (Note: Overrides pgpol.configuration)	nil (The value is evaluated as a template)
pgpool.useLoadBalancing	If true, use Pgpool Load-Balancing	true
LDAP
ldap.enabled	Enable LDAP support	false
ldap.existingSecret	Name of existing secret to use for LDAP passwords	nil
ldap.uri	LDAP URL beginning in the form ldap[s]://<hostname>:<port>	nil
ldap.base	LDAP base DN	nil
ldap.binddn	LDAP bind DN	nil
ldap.bindpw	LDAP bind password	nil
ldap.bslookup	LDAP base lookup	nil
ldap.scope	LDAP search scope	nil
ldap.tlsReqcert	LDAP TLS check on server certificates	nil
ldap.nssInitgroupsIgnoreusers	LDAP ignored users	root,nslcd
Prometheus metrics
metricsImage.registry	Registry for PostgreSQL Prometheus exporter	docker.io
metricsImage.repository	Repository for PostgreSQL Prometheus exporter	bitnami/postgres-exporter
metricsImage.tag	Tag for PostgreSQL Prometheus exporter	{TAG_NAME}
metricsImage.pullPolicy	PostgreSQL Prometheus exporter image pull policy	IfNotPresent
metricsImage.pullSecrets	Specify docker-registry secret names as an array	[] (does not add image pull secrets to deployed pods)
metricsImage.debug	Specify if debug logs should be enabled	false
metrics.securityContext.enabled	Enable security context for PostgreSQL Prometheus exporter	true
metrics.securityContext.runAsUser	User ID for the PostgreSQL Prometheus exporter container	1001
metrics.resources	The [resources] to allocate for container	{}
metrics.livenessProbe	Liveness probe configuration for PostgreSQL Prometheus exporter	Check values.yaml file
metrics.readinessProbe	Readiness probe configuration for PostgreSQL Prometheus exporter	Check values.yaml file
metrics.annotations	Annotations for PostgreSQL Prometheus exporter service	{prometheus.io/scrape: "true", prometheus.io/port: "9187"}
metrics.serviceMonitor.enabled	if true, creates a Prometheus Operator ServiceMonitor (also requires metrics.enabled to be true)	false
metrics.serviceMonitor.namespace	Optional namespace which Prometheus is running in	nil
metrics.serviceMonitor.interval	How frequently to scrape metrics (use by default, falling back to Prometheus' default)	nil
metrics.serviceMonitor.selector	Default to kube-prometheus install (CoreOS recommended), but should be set according to Prometheus install	{prometheus: "kube-prometheus"}
Init Container to adapt volume permissions
volumePermissionsImage.registry	Registry for Bitnami Minideb	docker.io
volumePermissionsImage.repository	Repository for Bitnami Minideb	bitnami/minideb
volumePermissionsImage.tag	Tag for Bitnami Minideb	latest
volumePermissionsImage.pullPolicy	Bitnami Minideb exporter image pull policy	Always
volumePermissionsImage.pullSecrets	Specify docker-registry secret names as an array	[] (does not add image pull secrets to deployed pods)
volumePermissions.enabled	Enable init container to adapt volume permissions	false
volumePermissions.securityContext.enabled	Enable security context for Bitnami Minideb	false
volumePermissions.securityContext.runAsUser	User ID for the Bitnami Minideb container	0
Persistence
persistence.enabled	Enable data persistence	true
persistence.existingClaim	Use a existing PVC which must be created manually before bound	nil
persistence.storageClass	Specify the storageClass used to provision the volume	nil
persistence.mountPath	Path to mount data volume at	nil
persistence.accessMode	Access mode of data volume	ReadWriteOnce
persistence.size	Size of data volume	8Gi
persistence.annotations	Persistent Volume Claim annotations	{}
Expose
service.type	Kubernetes service type (ClusterIP, NodePort or LoadBalancer)	ClusterIP
service.port	PostgreSQL port	5432
service.nodePort	Kubernetes service nodePort	nil
service.annotations	Annotations for PostgreSQL service	{}
service.loadBalancerIP	loadBalancerIP if service type is LoadBalancer	nil
service.loadBalancerSourceRanges	Address that are allowed when service is LoadBalancer	[]
service.clusterIP	Static clusterIP or None for headless services	nil
ingress.enabled	Enable ingress controller resource	false
ingress.certManager	Add annotations for cert-manager	false
ingress.annotations	Ingress annotations	[]
ingress.hosts[0].name	Hostname for PostgreSQL service	postgresql.local
ingress.hosts[0].path	Path within the url structure	/
ingress.tls[0].hosts[0]	TLS hosts	postgresql.local
ingress.tls[0].secretName	TLS Secret (certificates)	postgresql.local-tls
ingress.secrets[0].name	TLS Secret Name	nil
ingress.secrets[0].certificate	TLS Secret Certificate	nil
ingress.secrets[0].key	TLS Secret Key	nil
networkPolicy.enabled	Enable NetworkPolicy	false
networkPolicy.allowExternal	Don't require client label for connections	true

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

$ helm install my-release \
    --set postgresql.password=password \
    bitnami/postgresql-ha

The above command sets the password for user postgres to password.

Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,

$ helm install my-release -f values.yaml bitnami/postgresql-ha

Configuration and installation details

Rolling VS Immutable tags

It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.

Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.

Production configuration and horizontal scaling

This chart includes a values-production.yaml file where you can find some parameters oriented to production configuration in comparison to the regular values.yaml:

• Enable Newtworkpolicy blocking external access:

- networkPolicy.enabled: false
+ networkPolicy.enabled: true
- networkPolicy.allowExternal: true
+ networkPolicy.allowExternal: false

• Start a side-car prometheus exporter:

- metrics.enabled: false
+ metrics.enabled: true

To horizontally scale this chart, you can use the --replicaCount flag to modify the number of nodes in your PostgreSQL deployment. Also you can use the values-production.yaml file or modify the parameters shown above.

Change PostgreSQL version

To modify the PostgreSQL version used in this chart you can specify a valid image tag using the image.tag parameter. For example, image.tag=12.0.0

Configure the way how to expose PostgreSQL

• Ingress: The ingress controller must be installed in the Kubernetes cluster. Set ingress.enabled=true to expose PostgreSQL through Ingress.
• ClusterIP: Exposes the service on a cluster-internal IP. Choosing this value makes the service only reachable from within the cluster. Set service.type=ClusterIP to choose this service type.
• NodePort: Exposes the service on each Node's IP at a static port (the NodePort). You’ll be able to contact the NodePort service, from outside the cluster, by requesting NodeIP:NodePort. Set service.type=NodePort to choose this service type.
• LoadBalancer: Exposes the service externally using a cloud provider's load balancer. Set service.type=LoadBalancer to choose this service type.

Adjust permissions of persistent volume mountpoint

As the images run as non-root by default, it is necessary to adjust the ownership of the persistent volumes so that the containers can write data into it.

By default, the chart is configured to use Kubernetes Security Context to automatically change the ownership of the volume. However, this feature does not work in all Kubernetes distributions. As an alternative, this chart supports using an initContainer to change the ownership of the volume before mounting it in the final destination.

You can enable this initContainer by setting volumePermissions.enabled to true.

LDAP

LDAP support can be enabled in the chart by specifying the ldap. parameters while creating a release. The following parameters should be configured to properly enable the LDAP support in the chart.

• ldap.enabled: Enable LDAP support. Defaults to false.
• ldap.uri: LDAP URL beginning in the form ldap[s]://<hostname>:<port>. No defaults.
• ldap.base: LDAP base DN. No defaults.
• ldap.binddn: LDAP bind DN. No defaults.
• ldap.bindpw: LDAP bind password. No defaults.
• ldap.bslookup: LDAP base lookup. No defaults.
• ldap.nss_initgroups_ignoreusers: LDAP ignored users. root,nslcd.
• ldap.scope: LDAP search scope. No defaults.
• ldap.tls_reqcert: LDAP TLS check on server certificates. No defaults.

For example:

ldap.enabled="true"
ldap.uri="ldap://my_ldap_server"
ldap.base="dc=example\,dc=org"
ldap.binddn="cn=admin\,dc=example\,dc=org"
ldap.bindpw="admin"
ldap.bslookup="ou=group-ok\,dc=example\,dc=org"
ldap.nss_initgroups_ignoreusers="root\,nslcd"
ldap.scope="sub"
ldap.tls_reqcert="demand"

Next, login to the PostgreSQL server using the psql client and add the PAM authenticated LDAP users.

Note: Parameters including commas must be escaped as shown in the above example. More information at: https://github.com/helm/helm/blob/master/docs/using_helm.md#the-format-and-limitations-of---set

repmgr.conf / postgresql.conf / pg_hba.conf / pgpool.conf files as configMap

This helm chart also supports to customize the whole configuration file.

Add your custom files to "files" in your working directory. Those files will be mounted as configMap to the containers and it will be used for configuring Pgpool, Repmgr and the PostgreSQL server.

Alternatively, you can specify the Pgpool, PostgreSQL and Repmgr configuration using the pgpool.configuration, postgresql.configuration, postgresql.pgHbaConfiguration, and postgresql.repmgrConfiguration parameters.

In addition to these options, you can also set an external ConfigMap(s) with all the configuration files. This is done by setting the postgresql.configurationCM and pgpool.configurationCM parameters. Note that this will override the two previous options.

Allow settings to be loaded from files other than the default postgresql.conf

If you don't want to provide the whole PostgreSQL configuration file and only specify certain parameters, you can add your extended .conf files to "files/conf.d/" in your working directory. Those files will be mounted as configMap to the containers adding/overwriting the default configuration using the include_dir directive that allows settings to be loaded from files other than the default postgresql.conf.

Alternatively, you can specify the extended configuration using the postgresql.extendedConf parameter.

In addition to these options, you can also set an external ConfigMap with all the extra configuration files. This is done by setting the postgresql.extendedConfCM parameter. Note that this will override the two previous options.

Initialize a fresh instance

The Bitnami PostgreSQL with Repmgr image allows you to use your custom scripts to initialize a fresh instance. In order to execute the scripts, they must be located inside the chart folder files/docker-entrypoint-initdb.d so they can be consumed as a ConfigMap.

Alternatively, you can specify custom scripts using the initdbScripts parameter as dict.

In addition to these options, you can also set an external ConfigMap with all the initialization scripts. This is done by setting the postgresql.initdbScriptsCM parameter. Note that this will override the two previous options. If your initialization scripts contain sensitive information such as credentials or passwords, you can use the initdbScriptsSecret parameter.

The allowed extensions are .sh, .sql and .sql.gz.

Use of global variables

In more complex scenarios, we may have the following tree of dependencies

                     +--------------+
                     |              |
        +------------+   Chart 1    +-----------+
        |            |              |           |
        |            --------+------+           |
        |                    |                  |
        |                    |                  |
        |                    |                  |
        |                    |                  |
        v                    v                  v
+-------+------+    +--------+------+  +--------+------+
|              |    |               |  |               |
|PostgreSQL HA |    |  Sub-chart 1  |  |  Sub-chart 2  |
|              |    |               |  |               |
+--------------+    +---------------+  +---------------+

The three charts below depend on the parent chart Chart 1. However, subcharts 1 and 2 may need to connect to PostgreSQL HA as well. In order to do so, subcharts 1 and 2 need to know the PostgreSQL HA credentials, so one option for deploying could be deploy Chart 1 with the following parameters:

postgresql.postgresqlPassword=testtest
subchart1.postgresql.postgresqlPassword=testtest
subchart2.postgresql.postgresqlPassword=testtest
postgresql.postgresqlDatabase=db1
subchart1.postgresql.postgresqlDatabase=db1
subchart2.postgresql.postgresqlDatabase=db1

If the number of dependent sub-charts increases, installing the chart with parameters can become increasingly difficult. An alternative would be to set the credentials using global variables as follows:

global.postgresql.postgresqlPassword=testtest
global.postgresql.postgresqlDatabase=db1

This way, the credentials will be available in all of the subcharts.

Persistence

The data is persisted by default using PVC templates in the PostgreSQL statefulset. You can disable the persistence setting the persistence.enabled parameter to false. A default StorageClass is needed in the Kubernetes cluster to dynamically provision the volumes. Specify another StorageClass in the persistence.storageClass or set persistence.existingClaim if you have already existing persistent volumes to use.

Upgrade

It's necessary to specify the existing passwords while performing a upgrade to ensure the secrets are not updated with invalid randomly generated passwords. Remember to specify the existing values of the postgresql.password and postgresql.repmgrPassword parameters when upgrading the chart:

$ helm upgrade my-release bitnami/postgresql-ha \
    --set postgresql.password=[POSTGRESQL_PASSWORD] \
    --set postgresql.repmgrPassword=[REPMGR_PASSWORD]

Note: you need to substitute the placeholders [POSTGRESQL_PASSWORD], and [REPMGR_PASSWORD] with the values obtained from instructions in the installation notes.

2.0.0

The Bitnami Pgpool image was migrated to a "non-root" user approach. Previously the container ran as the root user and the Pgpool daemon was started as the pgpool user. From now on, both the container and the Pgpool daemon run as user 1001. You can revert this behavior by setting the parameters pgpool.securityContext.runAsUser, and pgpool.securityContext.fsGroup to 0.

Consequences:

• No backwards compatibility issues are expected since all the data is at PostgreSQL pods, and Pgpool uses a deployment without persistence. Therefore, upgrades should work smoothly from 1.x.x versions.
• Environment variables related to LDAP configuration were renamed removing the PGPOOL_ prefix. For instance, to indicate the LDAP URI to use, you must set LDAP_URI instead of PGPOOL_LDAP_URI

1.0.0

A new major version of repmgr (5.0.0) was included. To upgrade to this major version, it's necessary to upgrade the repmgr extension installed on the database. To do so, follow the steps below:

• Reduce your PostgreSQL setup to one replica (primary node) and upgrade to 1.0.0, enabling the repmgr extension upgrade:

$ helm upgrade my-release --version 1.0.0 bitnami/postgresql-ha \
    --set postgresql.password=[POSTGRESQL_PASSWORD] \
    --set postgresql.repmgrPassword=[REPMGR_PASSWORD] \
    --set postgresql.replicaCount=1 \
    --set postgresql.upgradeRepmgrExtension=true

• Scale your PostgreSQL setup to the original number of replicas:

$ helm upgrade my-release --version 1.0.0 bitnami/postgresql-ha \
    --set postgresql.password=[POSTGRESQL_PASSWORD] \
    --set postgresql.repmgrPassword=[REPMGR_PASSWORD] \
    --set postgresql.replicaCount=[NUMBER_OF_REPLICAS]

Note: you need to substitute the placeholders [POSTGRESQL_PASSWORD], and [REPMGR_PASSWORD] with the values obtained from instructions in the installation notes.

0.4.0

In this version, the chart will use PostgreSQL-Repmgr container images with the Postgis extension included. The version used in Postgresql version 10, 11 and 12 is Postgis 2.5, and in Postgresql 9.6 is Postgis 2.3. Postgis has been compiled with the following dependencies:

• protobuf
• protobuf-c
• json-c
• geos
• proj
• gdal