respond to review
This commit is contained in:
parent
4088e0090f
commit
64e1640f11
|
|
@ -39,7 +39,7 @@ Those parameters are grouped under the `metadata` top-level key.
|
||||||
|
|
||||||
## Top-level parameters
|
## Top-level parameters
|
||||||
|
|
||||||
Those are parameters grouped directly under the `spec` key in the manifest.
|
These are parameters are grouped directly under the `spec` key in the manifest.
|
||||||
|
|
||||||
* **teamId**
|
* **teamId**
|
||||||
name of the team the cluster belongs to. Changing it after the cluster
|
name of the team the cluster belongs to. Changing it after the cluster
|
||||||
|
|
|
||||||
|
|
@ -316,4 +316,4 @@ If you add
|
||||||
logical_backup:
|
logical_backup:
|
||||||
enable_logical_backup: true
|
enable_logical_backup: true
|
||||||
```
|
```
|
||||||
to the cluster manifest, the operator will start a k8s cron job that will periodically execute `pg_dumpall` on the target PG cluster and upload 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 for details.
|
to the cluster manifest, the operator will start a k8s cron job that will periodically execute `pg_dumpall` on the target PG cluster and upload 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.
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue