Are all patroni parameters supported? Use of pgbackrest for backup and restore.

• Which image of the operator are you using?
  registry.opensource.zalan.do/acid/postgres-operator:v1.5.0
• Where do you run it - cloud or metal? Kubernetes or OpenShift?
  Kubernetes in Centos8 vm.
• Are you running Postgres Operator in production?
  Yes
• Type of issue?
  Question

Hi

I'm looking to use pgbackrest along with the zalando postgres-operator.
The use case is to take backups (full and incremental) and do a PITR when need be.

I have a few questions:

1. I'd like to know if the operator supports all patroni parameters (for example 'archive_command' as shown here)?
   1.1. If not, I can have another container that patches the patroni config at http://localhost:8008/config to update the parameter(s); Would that trigger a restart / reload of config in postgres? If not, how do you go request the operator to reload the configuration?
2. Is there any plan to support pgbackrest natively in the operator in future?
3. How do you request the operator to stop the database cluster so that pgbackrest restore can be executed and then request the operator to startup the database to do the restore automatically?

Thanks.

Edit1:
I may be wrong, but I see https://github.com/zalando/postgres-operator/blob/v1.5.0/pkg/cluster/k8sres.go#L409 and https://github.com/zalando/postgres-operator/blob/v1.5.0/pkg/cluster/sync.go#L440 and feel like not all patroni parameters are supported. - IGNORE

Edit2:
It looks like I can just add an "archive_command" under spec.postgresql.parameters in the manifest for a database cluster and operator handles it.

Review the referenced pkg/cluster/k8sres.go and pkg/cluster/sync.go code, along with the spec.postgresql.parameters configuration mentioned in the issue. Determine which Patroni and pgBackRest settings and restore operations are supported, then document the supported workflow and any limitations.