fix minor issues in docs and manifests

docs/reference/cluster_manifest.md

@@ -184,7 +184,7 @@ explanation of `ttl` and `loop_wait` parameters.
   ```
   hostssl all +pamrole all pam
   ```
-  , where pamrole is the name of the role for the pam authentication; any
+  where pamrole is the name of the role for the pam authentication; any
   custom `pg_hba` should include the pam line to avoid breaking pam
   authentication. Optional.
 
@@ -379,4 +379,4 @@ Those parameters are grouped under the `tls` top-level key.
 
 * **caFile**
   Optional filename to the CA certificate. Useful when the client connects
-  with `sslmode=verify-ca` or `sslmode=verify-full`.
+  with `sslmode=verify-ca` or `sslmode=verify-full`. Default is empty.

docs/user.md

@@ -30,7 +30,7 @@ spec:
   databases:
     foo: zalando
   postgresql:
-    version: "11"
+    version: "12"
 ```
 
 Once you cloned the Postgres Operator [repository](https://github.com/zalando/postgres-operator)
@@ -515,9 +515,9 @@ executed.
 ## Custom TLS certificates
 
 By default, the spilo image generates its own TLS certificate during startup.
-This certificate is not secure since it cannot be verified and thus doesn't
-protect from active MITM attacks. In this section we show how a Kubernete
-Secret resources can be loaded with a custom TLS certificate.
+However, this certificate cannot be verified and thus doesn't protect from
+active MITM attacks. In this section we show how to specify a custom TLS
+certificate which is mounted in the database pods via a K8s Secret.
 
 Before applying these changes, the operator must also be configured with the
 `spilo_fsgroup` set to the GID matching the postgres user group. If the value

manifests/complete-postgres-manifest.yaml

@@ -22,7 +22,7 @@ spec:
   databases:
     foo: zalando
   postgresql:
-    version: "11"
+    version: "12"
     parameters: # Expert section
       shared_buffers: "32MB"
       max_connections: "10"

manifests/minimal-postgres-manifest.yaml

@@ -16,4 +16,4 @@ spec:
   databases:
     foo: zalando  # dbname: owner
   postgresql:
-    version: "11"
+    version: "12"

manifests/standby-manifest.yaml

@@ -9,7 +9,7 @@ spec:
     size: 1Gi
   numberOfInstances: 1
   postgresql:
-    version: "11"
+    version: "12"
 # Make this a standby cluster and provide the s3 bucket path of source cluster for continuous streaming.
   standby:
     s3_wal_path: "s3://path/to/bucket/containing/wal/of/source/cluster/"

ui/manifests/deployment.yaml

@@ -20,7 +20,7 @@ spec:
       serviceAccountName: postgres-operator-ui
       containers:
         - name: "service"
-          image: registry.opensource.zalan.do/acid/postgres-operator-ui:v1.3.0
+          image: registry.opensource.zalan.do/acid/postgres-operator-ui:v1.4.0
           ports:
             - containerPort: 8081
               protocol: "TCP"