From d30dd9e5e51b7f567968e20d596bf1fd81f7d3e9 Mon Sep 17 00:00:00 2001 From: Sergey Dudoladov Date: Fri, 5 Apr 2019 11:02:44 +0200 Subject: [PATCH] Document S3 bucket for logical backups --- docs/reference/operator_parameters.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/operator_parameters.md b/docs/reference/operator_parameters.md index 519b58ef4..9d1973057 100644 --- a/docs/reference/operator_parameters.md +++ b/docs/reference/operator_parameters.md @@ -488,7 +488,7 @@ scalyr sidecar. In the CRD-based configuration they are grouped under the Docker image for the pods of the cron job. Must implement backup/uploading logic. Default: empty. * **logical_backup_s3_bucket** - S3 bucket to store backup results. Default: same as the bucket as for WAL. + S3 bucket to store backup results. The bucket has to be present and accessible by Postgres pods. Default: empty. For the configmap operator configuration, the [default parameter values](https://github.com/zalando-incubator/postgres-operator/blob/master/pkg/util/config/config.go#L14) mentioned here are likely to be overwritten in your local operator installation via your local version of the operator configmap. In the case you use the operator CRD, all the CRD defaults are provided in the [operator's default configuration manifest](https://github.com/zalando-incubator/postgres-operator/blob/master/manifests/postgresql-operator-default-configuration.yaml)