Tags give the ability to mark specific points in history as being important
-
-
v0.8.2
88d1bb40 · ·v0.8.2 Bugfix release, these are the changes since 0.7.x: Added * Validate `values` schema * Ability to run custom `post_init` scripts * GitHub actions linting the Helm Charts as well as shellcheck the shell scripts * Prevent full WAL disks (experimental, disabled by default) * Allow pgBouncer customization (pg_hba, user list) Changed * Update multinode Chart to work with TimescaleDB 2.0.0 * Use Parallel [podManagementPolicy](https://v1-18.docs.kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/#statefulsetspec-v1-apps) for faster scale-up/down. * Explicitly set [(Pod)securityContext](https://v1-18.docs.kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/#podsecuritycontext-v1-core)
-
v0.8.1
254fc3ed · ·v0.8.1 Added * Validate `values` schema * Ability to run custom `post_init` scripts * GitHub actions linting the Helm Charts as well as shellcheck the shell scripts * Prevent full WAL disks (experimental, disabled by default) * Allow pgBouncer customization (pg_hba, user list) Changed * Update multinode Chart to work with TimescaleDB 2.0.0 * Use Parallel [podManagementPolicy](https://v1-18.docs.kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/#statefulsetspec-v1-apps) for faster scale-up/down. * Explicitly set [(Pod)securityContext](https://v1-18.docs.kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/#podsecuritycontext-v1-core)
-
v0.7.0
dd031506 · ·Release v0.7.0 The reason for the bump in minor version is that the default PostgreSQL version is changed from 11 to 12, which is an incompatible change for older deployments. Added * The possibility to run a [`pgBouncer`](https://www.pgbouncer.org/) container in every Pod. * Allow clusters to be initialized from a backup Changed * Use the PostgreSQL 12 Docker Image by default * Use `lz4` compression method by default for pgBackRest
-
v0.6.2
2ff36665 · ·Stamp release v0.6.2 Added * Allow the full Service Spec for the primary and replica Service to be customized in `values.yaml` Changed * `timescaledb-tune` is now enabled by default * Default autovacuum parameters are changed to better support many chunks * Default the pull policy for the Docker Images to `Always`. This is mainly useful during development Fixed * Prevent noise in the diagnostic logs about missing files and very short vacuum runs
-
v0.6.1
eef80bff · ·Stamp release v0.6.1 Added * Name for PostgreSQL container port, allows for easier `kubectl port-forward` * Backup parameter examples around encryption Fixed * Include kustomize/example directory in the Helm artifacts. This includes new tarballs for recent releases. * Allow `generate_kustomization.sh` to run on MacOS
-
-
v0.5.5
6014f5c9 · ·Release v0.5.5 Added * Issue CHECKPOINTs when terminating a Pod to improve time to recover * Add possibility to specify LoadBalancer port * Allow mounting `/dev/shm` from Memory, allows bigger Parallel Query workloads * Ability to generate Secrets outside of Helm. This lays the groundwork for removing plain text secrets from the Helm deployment. Fixed * Anti-Affinity clause was using the wrong name to match pods, causing unbalanced deployments -
v0.5.4
d38c5c69 · ·Release v0.5.4 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](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/#configure-all-key-value-pairs-in-a-configmap-as-container-environment-variables) 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 9708c38b, it is now much more likely that environment variables are exposed to the PostgreSQL processes. -
v0.5.1
9bf6d6f0 · ·Release v0.5.1 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)