postgres-operator/manifests
Oleksii Kliukin 8b85935a7a Allow cloning clusters from the operator. (#90)
Allow cloning clusters from the operator.

The changes add a new JSON node `clone` with possible values `cluster`
and `timestamp`. `cluster` is mandatory, and setting a non-empty
`timestamp` triggers wal-e point in time recovery. Spilo and Patroni do
the whole heavy-lifting, the operator just defines certain variables and
gathers some data about how to connect to the host to clone or the
target S3 bucket.

As a minor change, set the image pull policy to IfNotPresent instead
of Always to simplify local testing.

Change the default replication username to standby.
2017-09-08 16:47:03 +02:00
..
configmap.yaml Allow cloning clusters from the operator. (#90) 2017-09-08 16:47:03 +02:00
fake-teams-api.yaml remove new line from the token; 2017-05-12 16:38:42 +02:00
infrastructure-roles.yaml Feature/infrastructure roles (#91) 2017-05-12 11:41:33 +02:00
platform-credentials.yaml Pod Rolling update 2017-05-12 11:41:25 +02:00
postgres-operator.yaml set image pull policy to ifnotpresent 2017-05-12 16:38:42 +02:00
serviceaccount.yaml Make example manifests minikube-friendly. 2017-05-12 11:41:28 +02:00
testpostgresql.yaml Configure load balancer on a per-cluster and operator-wide level (#57) 2017-06-30 13:38:49 +02:00