[v0.5.4] - 2020-02-28

Added

• Examples for setting up a High Throughput Cluster, or using different backup parameters
• Ability to override archive-push/archive-get pgBackRest settings
• Ability to use envFrom to specify environment variables

Changed

• Update references to the latest Docker image (PostgreSQL 11.7). This also means PostGIS is now included
  in the default Docker Image

Fixed

• Remove all non-PostgreSQL/Kubernetes environment variables from Patroni/PostgreSQL
  A regular user in PostgreSQL has the ability to read the environment variables of the
  postmaster. Up to now, the chance of leaking secrets would have been small, but with
  commit 9708c38, it is now much more likely that environment variables are exposed
  to the PostgreSQL processes.

[v0.5.3] - 2020-02-04

NOTICE: When migrating from a < 0.5.x chart, the config Service needs to be removed before
invoking helm update, as the update will otherwise fail.

kubectl delete service/${RELEASE}-config
helm upgrade --install [...]

Changed

• Set autotune max_wal_size to 60% (instead of 80%) for a dedicated WAL volume

Fixed

• Prevent creation of replication slots for Jobs

[v0.5.2] - 2020-01-31

NOTICE: When migrating from a < 0.5.x chart, the config Service needs to be removed before
invoking helm update, as the update will otherwise fail.

kubectl delete service/${RELEASE}-config
helm upgrade --install [...]

Added

• Support for multiple tablespaces at initialization time

Fixed

• CronJob triggering the backup (the POST request was not valid json)

[v0.5.1] - 2020-01-21

NOTICE: When migrating from a < 0.5.x chart, the config Service needs to be removed before
invoking helm update, as the update will otherwise fail.

kubectl delete service/${RELEASE}-config
helm upgrade --install [...]

Added

• Optionally tune PostgreSQL settings (e.g. shared_buffers, work_mem, max_wal_size) using timescaledb-tune
• The charts are now also available in a Helm Repository

Changed

• The Service for the primary is now also created and managed by Helm
• Use TimescaleDB 1.6 as the default version

Fixed

• Configuration changes in patroni.bootstrap.dcs now propagate to PostgreSQL servers, previously these settings
  were only read during bootstrap.
• Patroni can now also use the endpoint in OpenShift
• pgBackRest will not check its stanza on a replica
• Default Backup Schedule is now set to 1 full a week and 6 incremental backups. (The previous definition mixed up
  day of month with day of week)

[v0.4.0] - 2019-12-12

Added

• Enabling Prometheus now creates a Service that can be properly scraped
• Support for NetworkPolicy

Changed

• Switch services to ClusterIP if the Load Balancer is set to disabled
• Create PGDATA and WALDIR before a pgBackRest restore

[v0.3.0] - 2019-11-25

NOTICE: When migrating from a 0.2.x chart to a 0.3 chart, please take the following into account:

• if you use the env key in your values, you should rewrite them from a
  plain dict into a list of EnvVar

Added

• Add ability to annotate pods in the StatefulSet
• Add ability to run any script as callback, if exposed as a ConfigMap

Changed

• Reduce loglevel of Patroni from INFO to WARNING
• The values.yaml env key should be expressed as a list of EnvVars
• Refer to the latest minor versions for PostgreSQL & TimescaleDB

Fixed

• Set unix_socket_permissions using PostgreSQL parameters instead

[v0.2.5] - 2019-11-06

Added

• Add readiness probe for PostgreSQL
• Allow a (debug) command to run at container startup
• Add a Headless Service (by default),
  with the option to convert it into a Load Balancer

Changed

• Rename backup.enable to backup.enabled for consistency, the old naming does still work.
• Rename postgresExporter to prometheus

[v0.2.4] - 2019-11-05

Changed

• Use 2.0.0-beta3 Docker Image for multinode
• Allow postgres-exporter to run as a sidecar

[v0.2.3] - 2019-11-01

Added

• Allow annotations to be specified for the Load Balancer in the values.yaml file

[v0.2.2] - 2019-10-31

Changed

• Use TimescaleDB 1.5 Docker image by default