Update documentation on E2E

Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>

docs/src/e2e.md

@@ -29,8 +29,8 @@ and the following suite of E2E tests are performed on that cluster:
 * Creation of a `Cluster`;
 * Usage of a persistent volume for data storage;
 * Connection via services, including read-only;
-* Scale-up of a `Cluster`;
-* Scale-down of a `Cluster`;
+* Connection via certificates generated by `kubectl-cnp`;
+* Scale-up and scale-down of a `Cluster`;
 * Failover;
 * Switchover;
 * Manage PostgreSQL configuration changes;
@@ -41,12 +41,17 @@ and the following suite of E2E tests are performed on that cluster:
 * Pod affinity using `NodeSelector`;
 * Metrics collection;
 * Operator pod deletion;
+* JSON log format;
+* Operator configuration via ConfigMap;
+* Operator pod eviction;
+* Operator upgrade;
 * Primary endpoint switch in case of failover in less than 10 seconds;
 * Primary endpoint switch in case of switchover in less than 20 seconds;
 * Recover from a degraded state in less than 60 seconds.
 
-The E2E tests suite is also run for OpenShift 4.6 and the latest Kubernetes
-and PostgreSQL releases on clusters created on the following services:
+The E2E tests suite is also run for OpenShift versions 4.5, 4.6, and 4.7
+and the latest Kubernetes and PostgreSQL releases on clusters created on the
+following services:
 
 * Google GKE
 * Amazon EKS

docs/src/release_notes.md

@@ -23,7 +23,7 @@ Changes:
   operator using the YAML manifest, you must delete the existing operator
   deployment before installing the new version. This is required to avoid
   conflicts with other Kubernetes API's due to a change in labels
-  and label selectors being directly managed by the  operator. Please refer to
+  and label selectors being directly managed by the operator. Please refer to
   the Cloud Native PostgreSQL documentation for additional detail on upgrading
   to 1.4.0
 - Fix the labels that are automatically defined by the operator, renaming them