Merge branch 'master' into lazy-update

docs/reference/cluster_manifest.md

@@ -140,10 +140,10 @@ These parameters are grouped directly under  the `spec` key in the manifest.
   is `false`, then no volume will be mounted no matter how operator was
   configured (so you can override the operator configuration). Optional.
 
-* **enableConnectionPool**
-  Tells the operator to create a connection pool with a database. If this
-  field is true, a connection pool deployment will be created even if
-  `connectionPool` section is empty. Optional, not set by default.
+* **enableConnectionPooler**
+  Tells the operator to create a connection pooler with a database. If this
+  field is true, a connection pooler deployment will be created even if
+  `connectionPooler` section is empty. Optional, not set by default.
 
 * **enableLogicalBackup**
   Determines if the logical backup of this cluster should be taken and uploaded
@@ -217,6 +217,12 @@ explanation of `ttl` and `loop_wait` parameters.
   automatically created by Patroni for cluster members and permanent replication
   slots. Optional.
 
+* **synchronous_mode**
+  Patroni `synchronous_mode` parameter value. The default is set to `false`. Optional.
+  
+* **synchronous_mode_strict**
+  Patroni `synchronous_mode_strict` parameter value. Can be used in addition to `synchronous_mode`. The default is set to `false`. Optional.
+  
 ## Postgres container resources
 
 Those parameters define [CPU and memory requests and limits](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/)
@@ -365,34 +371,35 @@ CPU and memory limits for the sidecar container.
   memory limits for the sidecar container. Optional, overrides the
   `default_memory_limits` operator configuration parameter. Optional.
 
-## Connection pool
+## Connection pooler
 
-Parameters are grouped under the `connectionPool` top-level key and specify
-configuration for connection pool. If this section is not empty, a connection
-pool will be created for a database even if `enableConnectionPool` is not
+Parameters are grouped under the `connectionPooler` top-level key and specify
+configuration for connection pooler. If this section is not empty, a connection
+pooler will be created for a database even if `enableConnectionPooler` is not
 present.
 
 * **numberOfInstances**
-  How many instances of connection pool to create.
+  How many instances of connection pooler to create.
 
 * **schema**
-  Schema to create for credentials lookup function.
+  Database schema to create for credentials lookup function.
 
 * **user**
-  User to create for connection pool to be able to connect to a database.
+  User to create for connection pooler to be able to connect to a database.
+  You can also choose a role from the `users` section or a system user role.
 
 * **dockerImage**
-  Which docker image to use for connection pool deployment.
+  Which docker image to use for connection pooler deployment.
 
 * **maxDBConnections**
   How many connections the pooler can max hold. This value is divided among the
   pooler pods.
 
 * **mode**
-  In which mode to run connection pool, transaction or session.
+  In which mode to run connection pooler, transaction or session.
 
 * **resources**
-  Resource configuration for connection pool deployment.
+  Resource configuration for connection pooler deployment.
 
 ## Custom TLS certificates
 

docs/reference/operator_parameters.md

@@ -84,6 +84,12 @@ Those are top-level keys, containing both leaf keys and groups.
   Patroni native Kubernetes support is used. The default is empty (use
   Kubernetes-native DCS).
 
+* **kubernetes_use_configmaps**
+  Select if setup uses endpoints (default), or configmaps to manage leader when
+  DCS is kubernetes (not etcd or similar). In OpenShift it is not possible to
+  use endpoints option, and configmaps is required. By default,
+  `kubernetes_use_configmaps: false`, meaning endpoints will be used.
+
 * **docker_image**
   Spilo Docker image for Postgres instances. For production, don't rely on the
   default image, as it might be not the most up-to-date one. Instead, build
@@ -601,39 +607,42 @@ scalyr sidecar. In the CRD-based configuration they are grouped under the
 * **scalyr_memory_limit**
   Memory limit value for the Scalyr sidecar. The default is `500Mi`.
 
-## Connection pool configuration
+## Connection pooler configuration
 
-Parameters are grouped under the `connection_pool` top-level key and specify
-default configuration for connection pool, if a postgres manifest requests it
+Parameters are grouped under the `connection_pooler` top-level key and specify
+default configuration for connection pooler, if a postgres manifest requests it
 but do not specify some of the parameters. All of them are optional with the
 operator being able to provide some reasonable defaults.
 
-* **connection_pool_number_of_instances**
-  How many instances of connection pool to create. Default is 2 which is also
+* **connection_pooler_number_of_instances**
+  How many instances of connection pooler to create. Default is 2 which is also
   the required minimum.
 
-* **connection_pool_schema**
-  Schema to create for credentials lookup function. Default is `pooler`.
+* **connection_pooler_schema**
+  Database schema to create for credentials lookup function to be used by the
+  connection pooler. Is is created in every database of the Postgres cluster.
+  You can also choose an existing schema. Default schema is `pooler`.
 
-* **connection_pool_user**
-  User to create for connection pool to be able to connect to a database.
-  Default is `pooler`.
+* **connection_pooler_user**
+  User to create for connection pooler to be able to connect to a database.
+  You can also choose an existing role, but make sure it has the `LOGIN`
+  privilege. Default role is `pooler`.
 
-* **connection_pool_image**
-  Docker image to use for connection pool deployment.
+* **connection_pooler_image**
+  Docker image to use for connection pooler deployment.
   Default: "registry.opensource.zalan.do/acid/pgbouncer"
 
-* **connection_pool_max_db_connections**
+* **connection_pooler_max_db_connections**
   How many connections the pooler can max hold. This value is divided among the
   pooler pods. Default is 60 which will make up 30 connections per pod for the
   default setup with two instances.
 
-* **connection_pool_mode**
-  Default pool mode, `session` or `transaction`. Default is `transaction`.
+* **connection_pooler_mode**
+  Default pooler mode, `session` or `transaction`. Default is `transaction`.
 
-* **connection_pool_default_cpu_request**
-  **connection_pool_default_memory_reques**
-  **connection_pool_default_cpu_limit**
-  **connection_pool_default_memory_limit**
-  Default resource configuration for connection pool deployment. The internal
+* **connection_pooler_default_cpu_request**
+  **connection_pooler_default_memory_reques**
+  **connection_pooler_default_cpu_limit**
+  **connection_pooler_default_memory_limit**
+  Default resource configuration for connection pooler deployment. The internal
   default for memory request and limit is `100Mi`, for CPU it is `500m` and `1`.