In the official docker image for pg11 the version of postgres is 11.13 while 11.15 has been released for a while.
As written in the docs:
This file has been truncated.
# Stolon inside kubernetes
In this example you'll see how stolon can provide an high available postgreSQL cluster inside kubernetes.
The sentinels and proxies will be deployed as [kubernetes deployments](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) while the keepers as a [kubernetes statefulset](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/).
## Docker image
Prebuilt images are available on the dockerhub, the images' tags are the stolon release version plus the postgresql version (for example v0.12.0-pg10).
**NOTE**: These images are **example** images provided for quickly testing stolon. In production you should build your own image customized to fit your needs (adding postgres extensions, backup tools/scripts etc...).
Additional images are available:
* `master-pg10`: automatically built after every commit to the master branch.
In the [image](image/docker) directory you'll find a Dockerfile to build the image used in this example (starting from the official postgreSQL images).
To build the image used in this example just execute (from the project root) `make` with the `docker` target providing the mandatory `PGVERSION` and `TAG` variables.
If I generate my own image with latest postgres on tag 0.17.0 is there something I should worry about?
Does Postgres 11.15 breaks any compatibility with stolon 0.17.0? (Most probably not as it is just a minor upgrade but just to be sure)