All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
These are changes that will probably be included in the next release.
- Switch services to ClusterIP if the Load Balancer is set to disabled
- Create PGDATA and WALDIR before a pgBackRest restore
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
- Add ability to annotate pods in the StatefulSet
- Add ability to run any script as callback, if exposed as a ConfigMap
- 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
- Set
unix_socket_permissions
using PostgreSQL parameters instead
- 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
- Rename backup.enable to backup.enabled for consistency, the old naming does still work.
- Rename postgresExporter to prometheus
- Use 2.0.0-beta3 Docker Image for multinode
- Allow postgres-exporter to run as a sidecar
- Allow annotations to be specified for the Load Balancer in the values.yaml file
- Use TimescaleDB 1.5 Docker image by default
- Point to the -latest Docker image tag for multinode by default
- Always explicitly set wal directory
- (multinode) Drop the TimescaleDB extension from the Data Nodes to allow a clean bootstrap to be done
- A preliminary multinode Helm chart
- Architecture diagrams
- Allow multiple volumes for the data directory and the WAL directory
- Documentation pgBackRest restore outside of Kubernetes environment
- The defined Patroni configuration is passed on (using a ConfigMap) to Patroni
- Secrets required by Patroni are injected using environment variables
- The defined pgBackRest configuration is passed on to pgBackRest (using a Secret as it holds credentials)
- The entrypoint no longer points to scripts in the Docker image, this pretty much allows any Docker image to be used, as long as it contains PostgreSQL, TimescaleDB, and pgBackRest
- Best practice PostgreSQL parameters, e.g. enable logging of connections by default
- Open Sourced this repository as Apache License 2.0
- Helm chart for
timescaledb-single
- Documentation for the
timescaledb-single
Helm chart