Release v0.13.0

Author: sgotti

CHANGELOG.md

@@ -1,5 +1,22 @@
 ### v0.13.0
 
+#### New features
+
+* Add a `stolonctl` command to force fail a keeper ([#546](https://github.com/sorintlab/stolon/pull/546))
+* Overcome PostgreSQL synchronous replication limitation that could cause lost transactions under some events ([#514](https://github.com/sorintlab/stolon/pull/514))
+* Users can now define `archiveRecoverySettings` in the cluster spec of a standby cluster. One of the possible use cases is to feed the standby cluster only with archived logs without streaming replication. (See Upgrade Notes) ([#543](https://github.com/sorintlab/stolon/pull/543))
+* Keeper: remove trailing new lines from provided passwords ([#548](https://github.com/sorintlab/stolon/pull/548))
+
+#### Bug Fixes
+
+* Sort keepers addresses in `pg_hba.conf` to avoid unneeded postgres instance reloads ([#558](https://github.com/sorintlab/stolon/pull/558))
+* Set `recovery_target_action` to promote when using recovery target settings [#545](https://github.com/sorintlab/stolon/pull/545))
+* Fixed wrong listen address used in `pg_hba.conf` when `SUReplAccessStrict` mode was enabled ([#520](https://github.com/sorintlab/stolon/pull/520))
+
+and [many other](https://github.com/sorintlab/stolon/milestone/12) bug fixes and documentation improvements.
+
+Thanks to everybody who contributed to this release.
+
 #### Upgrades notes.
 
 * The clusterspec `standbySettings` option as been replaced by the `standbyConfig` option. Internally it can contain two fields `standbySettings` and `archiveRecoverySettings` (see the clusterspec doc with the descriptors of this new option). If you're updating a standby cluster, BEFORE starting it you should update, using `stolonctl`, the clusterspec with the new `standbyConfig` option.

examples/kubernetes/stolon-keeper.yaml

@@ -21,7 +21,7 @@ spec:
       terminationGracePeriodSeconds: 10
       containers:
       - name: stolon-keeper
-        image: sorintlab/stolon:master-pg10
+        image: sorintlab/stolon:v0.13.0-pg10
         command:
           - "/bin/bash"
           - "-ec"

examples/kubernetes/stolon-proxy.yaml

@@ -15,7 +15,7 @@ spec:
     spec:
       containers:
       - name: stolon-proxy
-        image: sorintlab/stolon:master-pg10
+        image: sorintlab/stolon:v0.13.0-pg10
         command:
           - "/bin/bash"
           - "-ec"

examples/kubernetes/stolon-sentinel.yaml

@@ -15,7 +15,7 @@ spec:
     spec:
       containers:
       - name: stolon-sentinel
-        image: sorintlab/stolon:master-pg10
+        image: sorintlab/stolon:v0.13.0-pg10
         command:
           - "/bin/bash"
           - "-ec"

examples/swarm/docker-compose-pg.yml

@@ -8,7 +8,7 @@ secrets:
 
 services:
   sentinel:
-    image: sorintlab/stolon:master-pg10
+    image: sorintlab/stolon:v0.13.0-pg10
     command: gosu stolon stolon-sentinel --cluster-name stolon-cluster --store-backend=etcdv3 --store-endpoints http://etcd-00:2379,http://etcd-01:2379,http://etcd-02:2379 --log-level debug
     networks:
       - etcd_etcd
@@ -22,7 +22,7 @@ services:
         failure_action: pause
 
   keeper1:
-    image: sorintlab/stolon:master-pg10
+    image: sorintlab/stolon:v0.13.0-pg10
     hostname: keeper1
     environment:
       - PGDATA=/var/lib/postgresql/data
@@ -41,7 +41,7 @@ services:
 #        constraints: [node.labels.nodename == node1]
 
   keeper2:
-    image: sorintlab/stolon:master-pg10
+    image: sorintlab/stolon:v0.13.0-pg10
     hostname: keeper2
     environment:
       - PGDATA=/var/lib/postgresql/data
@@ -59,7 +59,7 @@ services:
 #        constraints: [node.labels.nodename == node2]
 
   proxy:
-    image: sorintlab/stolon:master-pg10
+    image: sorintlab/stolon:v0.13.0-pg10
     command: gosu stolon stolon-proxy --listen-address 0.0.0.0 --cluster-name stolon-cluster --store-backend=etcdv3 --store-endpoints http://etcd-00:2379,http://etcd-01:2379,http://etcd-02:2379 --log-level info
     networks:
       - etcd_etcd