Kubegres version 1.8

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

Kubegres version 1.7

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

Kubegres version 1.6

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

Kubegres version 1.5

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

Kubegres version 1.4

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

Kubegres version 1.3

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

Kubegres version 1.2

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

Kubegres version 1.1

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 is open source

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