minor doc fixes

This commit is contained in:
Sergey Dudoladov 2019-04-02 13:09:41 +02:00
parent 918860b6ea
commit 5d44904d14
2 changed files with 2 additions and 3 deletions

View File

@ -189,7 +189,7 @@ localhost:8080 by doing:
The inner 'query' gets the name of the postgres operator pod, and the outer
enables port forwarding. Afterwards, you can access the operator API with:
$ curl http://127.0.0.1:8080/$endpoint| jq .
$ curl --location http://127.0.0.1:8080/$endpoint | jq .
The available endpoints are listed below. Note that the worker ID is an integer
from 0 up to 'workers' - 1 (value configured in the operator configuration and

View File

@ -340,7 +340,6 @@ volumes that correspond to the previously running pods is not changed.
If you add
```
logical_backup:
enable_logical_backup: true
enableLogicalBackup: true
```
to the cluster manifest, the operator will create and sync the configuration of a k8s cron job that periodically executes `pg_dumpall` on the target PG cluster and uploads results to an S3 bucket. Note that due to the [limitation of Kubernetes cron jobs](https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#cron-job-limitations) it is highly advisable to set up additional monitoring for this feature; such monitoring is outside of the scope of operator responsibilities. See [configuration reference](reference/cluster_manifest.md) for details.