Add documentation and update manifests

docs/reference/cluster_manifest.md

@@ -166,6 +166,11 @@ These parameters are grouped directly under  the `spec` key in the manifest.
   If you set the `all` special item, it will be mounted in all containers (postgres + sidecars).
   Else you can set the list of target containers in which the additional volumes will be mounted (eg : postgres, telegraf)
   
+  * **statefulset_propagate_annotations**
+  An array of annotations from PostgresCRD that should be passed on to the statefulsets.
+  This also accepts the regular expression like downscaler/*, etc.
+  These annotations will also be passed to the connection-pooler deployments if any.
+
 ## Postgres parameters
 
 Those parameters are grouped under the `postgresql` top-level key, which is

docs/reference/operator_parameters.md

@@ -151,6 +151,11 @@ Those are top-level keys, containing both leaf keys and groups.
   [operator deployment manually](../../manifests/postgres-operator.yaml#L20).
   The default is `false`.
 
+* **statefulset_propagate_annotations**
+  An array of annotations from PostgresCRD that should be passed on to the statefulsets.
+  This also accepts the regular expression like downscaler/*, etc.
+  These annotations will also be passed to the connection-pooler deployments if any.
+
 ## Postgres users
 
 Parameters describing Postgres users. In a CRD-configuration, they are grouped