kubegres

We are pleased to announce the availability of Kubegres 1.18 with the following changes:

• #174: Added a new property 'serviceAccountName' in the YAML of 'kind: Kubegres'
• #176: Added a new property 'containerSecurityContext' of type v1.SecurityContext in the YAML of 'kind: Kubegres'

A special thanks to @toffentoffen and @CasperGN

We tested Kubegres with PostgreSql 16.2

This version is backward compatible with the previous versions of Kubegres.

To install and use Kubegres, please see: Getting started

We are pleased to announce the availability of Kubegres version 1.17

• Kubegres was updated to be compatible with PostgreSql 16.
• We upgraded the operator framework that Kubegres is developed with to Kubebuilder 3.12.0 (from 3.6.0).
• Kubegres was tested with a recent version of Kubernetes 1.27.3
• In addition to the existing 2 OS/ARCH "linux/amd64" and "linux/arm64", we added "linux/ppc64le" and "linux/s390x" in Docker

This release contains the following changes:

• #162: Postgres 16 error due to eliminated promote_trigger_file config parameter
• #165: Upgraded Kubegres to use the framework Kubebuilder 3.12.0

This version is backward compatible with the previous versions of Kubegres.

To install and use Kubegres, please see: Getting started

We are pleased to announce the availability of Kubegres version 1.16 with the following changes:

• #97: Replaced batch/v1beta1/Cronjob because it was deprecated from Kubernetes version 1.25
• #131: Upgraded Kubegres to use the framework Kubebuilder 3.6.0

Version 1.16 is only compatible with Kubernetes 1.21 or higher.

To install and use Kubegres, please see: Getting started

We are pleased to announce the availability of Kubegres version 1.15 with the following change:

• #72: Overwrite Readiness and Liveness config

A special thanks to @owenchenxy who reported and implemented the feature #72

Version 1.15 is compatible with any previous versions of Kubegres.

To install and use Kubegres, please see: Getting started

We are pleased to announce the availability of Kubegres version 1.14 with the following changes:

• #54 : The update of an existing Kubegres resource fails if the field 'resources' contains a value with a decimal point
• #69 : Kubegres operator crashes with blank spec.replicas

Thanks to @samstride for reporting the issue #54.

Thanks to @blushingpenguin for reporting the issue #69.

Version 1.14 is compatible with any previous versions of Kubegres.

To install and use Kubegres, please see: Getting started

We are pleased to announce the availability of Kubegres version 1.13 with the following changes:

• #52 : Allow setting the property 'securityContext' in the YAML of 'kind: Kubegres' in order to enable security policies in Postgres Pods
• #60 : Improve the failover process for replicas by replacing a replica which is reporting a health issue when the associated StatefulSet is still showing as deployed

A special thanks to @ylck for helping with the implementation of the feature #52.

Thanks to @teknologista for suggesting and testing the feature #52.

Thanks to @JuliuszJ for suggesting and testing the feature #60.

Version 1.13 is compatible with any previous versions of Kubegres.

To install and use Kubegres, please see: Getting started

We are pleased to announce the availability of Kubegres version 1.12 with the following changes:

• #40 : Allow setting the property 'wal_level' to 'logical' in postgres.conf
• #36 : Fix issue with the back-up logic which happened when a custom ConfigMap was set

Thanks to @pgvirtuoso for suggesting the feature #40.

Thanks to @anneum for reporting the issue #36 and his great help during the investigation.

Version 1.12 is compatible with any previous versions of Kubegres.

To install and use Kubegres, please see: Getting started

We are pleased to announce the availability of Kubegres version 1.11 with the following changes:

• #27 : Add support to manage volumes from Kubegres YAML
• #34 : Disable the codes to expand storage until Kubernetes enhancement kubernetes/enhancements#2842 is available

Thanks to @anneum for his help in testing #27 and his feedback about that feature.

Thanks to @patrickdung for suggesting the feature #27 so that it is possible to increase the memory size of /dev/shm.

Thanks to @aiesam for reporting the issues with expansion storage (#34)

Version 1.11 is compatible with any previous versions of Kubegres.

To install and use Kubegres, please see: Getting started

We are pleased to announce the availability of Kubegres version 1.10 with the following new features:

• #22 (PR #42) : Add support for resources requests/limits
• #43 : Increase the memory limit of Kubegres controller

A special thank to @ylck for implementing and helping testing the feature about resources requests/limits!

Thanks to @shubhamranjan for suggesting the feature about resources requests/limits.

Thanks to @edwardzjl for suggesting the feature about increasing the memory limit of Kubegres controller.

Version 1.10 is compatible with any previous versions of Kubegres.

To install and use Kubegres, please see: Getting started

We are pleased to announce the availability of Kubegres version 1.9 with the following new feature:

#17 : Set custom Node/Pod scheduling policy from Kubegres YAML. Added 2 new fields in YAML: 'scheduler.affinity and 'scheduler.tolerations'.

Thanks to @keithpenrod and @sshekghub for suggesting this new feature. And thanks to @sshekghub for helping with testing it!

Version 1.9 is compatible with any previous versions of Kubegres.

To install and use Kubegres, please see: Getting started

We are pleased to announce the availability of Kubegres version 1.8 with the following new feature:

#28 : Allow disabling automatic failover and allow to manually promote a Pod as Primary

Version 1.8 is compatible with any previous versions of Kubegres.

To install and use Kubegres, please see: Getting started

We are pleased to announce the availability of Kubegres version 1.7 with the following new feature:

#19 : Multi architecture support of Kubegres for linux/arm64 and linux/amd64

Thanks to @anthr76 for suggesting, implementing and helping testing this new feature.

Version 1.7 is compatible with any previous versions of Kubegres.

To install and use Kubegres, please see: Getting started

We are pleased to announce the availability of Kubegres version 1.6 with the following new feature:

#18 : When the field "spec.database.storageClassName" is omitted in Kubegres YAML, Kubegres operator should assign the default storageClass to the deployed PostgreSql cluster

Thanks to @mologie for suggesting and helping testing this new feature.

Version 1.6 is compatible with any versions of Kubegres from version 1.0

To install and use Kubegres, please see: Getting started

We are pleased to announce the availability of Kubegres version 1.5 with the following new feature:

#15 : When backup is enabled, set to the Pods created by the backup CronJob the custom annotations and env variables defined in a Kubegres YAML

Thanks to @laukaichung for suggesting and helping testing this new feature.

Version 1.5 is compatible with any versions of Kubegres from version 1.0

To install and use Kubegres, please see: Getting started

We are pleased to announce the availability of Kubegres version 1.4 with the following new feature:

#14 : Allow setting custom annotations from a Kubegres YAML and apply them to the Pods and StatefulSets.

Thanks to @laukaichung for suggesting and helping testing this new feature.

Version 1.4 is compatible with any versions of Kubegres from version 1.0

To install and use Kubegres, please see: Getting started

We are pleased to announce the availability of Kubegres version 1.3 with the following minor fix:

#13: The backup file name does not contain the kubegres resource name

Version 1.3 is compatible with any versions of Kubegres from version 1.0

To install and use Kubegres, please see: Getting started

We are pleased to announce the availability of Kubegres version 1.2 with the following bug fix:

#11 : Create a database folder 'pgdata' inside the 'volumeMount' folder to avoid errors with some storage classes. This issue does not happen with all storage classes but when it happens Postgres container cannot initialise.

Thanks to @timvol for suggesting and helping testing this new feature.

Version 1.2 is compatible with any versions of Kubegres from version 1.0

To install and use Kubegres, please see: Getting started

We are pleased to announce the availability of Kubegres version 1.1 with the following features based on the feedback of the open-source community:

• #4: Kubegres will only apply "pod anti-affinity" if there are sufficient nodes on a Kubernetes cluster. Otherwise, it will will deploy some PostgreSql instances on the same node(s). More details about Kubegres' pod anti-affinity here

• #5: In Kubegres yaml, we added the field 'imagePullSecrets' so that we can pull custom Postgres images from a private repo. The images have to be compatible with PostgreSql containers

A big thanks to the community for their kind feedback!

Version 1.1 is compatible with Kubegres version 1.0

To install and use it, please see: Getting started

Kubegres version 1.0 is open source and it provides the following features:

• It creates a cluster of PostgreSql servers with Streaming Replication enabled: it creates a Primary PostgreSql pod and a number of Replica PostgreSql pods and replicates primary's database in real-time to Replica pods.

• It manages fail-over: if a Primary PostgreSql crashes, it automatically promotes a Replica PostgreSql as a Primary.

• It has a data backup option allowing to dump PostgreSql data regularly in a given volume.

• It provides a very simple YAML with properties specialised for PostgreSql.

• It is resilient, has over 55 automatized tests cases and has been running in production.

• It works with the PostgreSql containers created by the Docker Official Images team. Kubegres uses the standard PostgreSql libraries to manage replication and failover and it does not require a custom Docker image with a set of third party libraries.

• It is portable because compatible with any Docker images which derive from the PostgreSql containers

To learn about how to install and use it, please visit the page: Getting started