From f9321f60fe0944e35c118597bd97507931c19b9b Mon Sep 17 00:00:00 2001 From: Simone Gotti Date: Tue, 27 Sep 2016 14:17:05 +0200 Subject: [PATCH] Release v0.3.0 --- CHANGELOG.md | 13 +++++++++++++ examples/kubernetes/README.md | 5 ++--- examples/kubernetes/stolon-keeper.yaml | 2 +- examples/kubernetes/stolon-proxy.yaml | 2 +- examples/kubernetes/stolon-sentinel.yaml | 2 +- 5 files changed, 18 insertions(+), 6 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index d67e16b7a..3e8a47563 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,4 +1,17 @@ +### v0.3.0 + +* Support multiple stores via [libkv](https://github.com/docker/libkv) ([#102](https://github.com/sorintlab/stolon/pull/102)). Currently etcd and consul are supported. +* Can use pg_rewind to sync slaves instead of doing a full resync ([#122](https://github.com/sorintlab/stolon/pull/122)). +* The `--initial-cluster-config` option has been added to the `stolon-sentinel` to provide an initial cluster configuration ([#107](https://github.com/sorintlab/stolon/pull/107)). +* A cluster config option for initializing the cluster also if multiple keepers are registred has been added ([#106](https://github.com/sorintlab/stolon/pull/106)). By default a sentinel won't initialize a new if multiple keepers are registered since it cannot know which one should be the master. With this option a random keeper will be choosed as the master. This is useful when an user wants to create a new cluster with an empty database and starting all the keeper together instead of having to start only one keeper, wait it to being elected as master and then starting the other keepers. +* The `--discovery-type` option has been added to the `stolon-sentinel` to choose if keeper discovery should be done using the store or kubernetes ([#129](https://github.com/sorintlab/stolon/pull/129)). +* Various options has been added to the `stolon-keeper` for setting postgres superuser, replication and initial superuser usernames and passwords ([#136](https://github.com/sorintlab/stolon/pull/136)). +* Numerous enhancements and bugfixes. + +Thanks to all the contributors! + + ### v0.2.0 * A stolon client (stolonctl) is provided. At the moment it can be used to get clusters list, cluster status and get/replace/patch cluster config ([#28](https://github.com/sorintlab/stolon/pull/28) [#64](https://github.com/sorintlab/stolon/pull/64)). In future multiple additional functions will be added. See [doc/stolonctl.md](doc/stolonctl.md). diff --git a/examples/kubernetes/README.md b/examples/kubernetes/README.md index 50514a00a..817e7953e 100644 --- a/examples/kubernetes/README.md +++ b/examples/kubernetes/README.md @@ -6,14 +6,13 @@ In this example you'll see how stolon can provide an high available postgreSQL c ## Docker image Prebuilt images are available on the dockerhub, the images' tags are their release version. Additional images are available: -* `latest`: latest released image (actually v0.2.0). +* `latest`: latest released image (actually v0.3.0). * `master`: automatically built after every commit to the master branch. In the [image](examples/kubernetes/image/docker) directory you'll find the Dockerfile to build the image used in this example. Once the image is built you should push it to the docker registry used by your kubernetes infrastructure. -`sorintlab/stolon:master` is the one used by the kubernetes definitions in this example. -For a more stable testing you can use `sorintlab/stolon:latest` +`sorintlab/stolon:v0.3.0` is the one used by the kubernetes definitions in this example. ### Keepers discovery diff --git a/examples/kubernetes/stolon-keeper.yaml b/examples/kubernetes/stolon-keeper.yaml index f6ddd2126..a1025a1ce 100644 --- a/examples/kubernetes/stolon-keeper.yaml +++ b/examples/kubernetes/stolon-keeper.yaml @@ -15,7 +15,7 @@ spec: spec: containers: - name: stolon-keeper - image: sorintlab/stolon:master + image: sorintlab/stolon:v0.3.0 env: - name: KEEPER value: "true" diff --git a/examples/kubernetes/stolon-proxy.yaml b/examples/kubernetes/stolon-proxy.yaml index d5f44aacb..df776fcb7 100644 --- a/examples/kubernetes/stolon-proxy.yaml +++ b/examples/kubernetes/stolon-proxy.yaml @@ -15,7 +15,7 @@ spec: spec: containers: - name: stolon-proxy - image: sorintlab/stolon:master + image: sorintlab/stolon:v0.3.0 env: - name: PROXY value: "true" diff --git a/examples/kubernetes/stolon-sentinel.yaml b/examples/kubernetes/stolon-sentinel.yaml index 01917e6e4..756cd4f60 100644 --- a/examples/kubernetes/stolon-sentinel.yaml +++ b/examples/kubernetes/stolon-sentinel.yaml @@ -15,7 +15,7 @@ spec: spec: containers: - name: stolon-sentinel - image: sorintlab/stolon:master + image: sorintlab/stolon:v0.3.0 env: - name: SENTINEL value: "true"