Release v0.12.0

CHANGELOG.md

@@ -1,6 +1,22 @@
 ### v0.12.0
 
-## Upgrades notes.
+#### New features
+
+* Detect and report when keeper persistent data dir is not the expected one (usually due to wrong configuration, non persistent storage etc...) ([#510](https://github.com/sorintlab/stolon/pull/510))
+* Support PostgresSQL 11 (beta) ([#513](https://github.com/sorintlab/stolon/pull/513))
+* Replication slots declared in the clusterspec `additionalMasterReplicationSlots` option will now be prefixed with the `stolon_` string to let users be able to manually create/drop custom replication slots (See Upgrade Notes) ([#531](https://github.com/sorintlab/stolon/pull/531))
+
+#### Bug Fixes
+
+* fix wrong address in pg_hba.conf when clusterspec `defaultSUReplAccessMode` is `strict` ([#520](https://github.com/sorintlab/stolon/pull/520))
+
+and [many other](https://github.com/sorintlab/stolon/milestone/11) bug fixes and documentation improvements.
+
+Thanks to everybody who contributed to this release:
+
+Alexandre Assouad, Lothar Gesslein, @nseyvet
+
+#### Upgrades notes.
 
 * Replication slots declared in the clusterspec `additionalMasterReplicationSlots` option will now be prefixed with the `stolon_` string to let users be able to manually create/drop custom replication slots (they shouldn't start with `stolon_`). Users of these feature should upgrade all the references to these replication slots adding the `stolon_` prefix.
 
@@ -24,7 +40,7 @@ Thanks to everybody who contributed to this release:
 Bill Helgeson, Niklas Hambüchen, Sylvere Richard, Tyler Kellen
 
 
-## Upgrades notes.
+#### Upgrades notes.
 
 * In the k8s store backend, the label that defines the kind of stolon component has changed from `app` to `component`. When upgrading you should update the various resource descriptors setting the k8s component name (`stolon-keeper`, `stolon-sentinel`, `stolon-proxy`) inside the `component` label instead of the `app` label.
 * When using the etcdv2 store, due to a wrong leader election path introduced in the last release and now fixed, if your sentinel returns an election error like `election loop error {"error": "102: Not a file ...` you should stop all the sentinels and remove the wrong dir using `etcdctl rmdir /stolon/cluster/$STOLONCLUSTER/sentinel-leader` where `$STOLONCLUSTER` should be substituted with the stolon cluster name (remember to set `ETCDCTL_API=2`).

README.md

@@ -52,14 +52,11 @@ Anyway it's quite easy to reset a cluster from scratch keeping the current maste
 
 ## Requirements
 
-* PostgreSQL 10 or 9 (9.4, 9.5, 9.6)
-* etcd2 >= v2.0, etcd3 >= v3.0, consul >= v0.6 or kubernetes 1.8 (based on the store you're going to use)
-
+* PostgreSQL 11, 10 or 9 (9.4, 9.5, 9.6)
+* etcd2 >= v2.0, etcd3 >= v3.0, consul >= v0.6 or kubernetes >= 1.8 (based on the store you're going to use)
 
 * OS: currently stolon is tested on GNU/Linux (with reports of people using it also on Solaris, *BSD and Darwin)
 
-
-
 ## build
 
 To build stolon we usually test and support the latest two major versions of Go like in the [Go release policy](https://golang.org/doc/devel/release.html#policy).

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.12.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.12.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.12.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.12.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.12.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.12.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.12.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