Update README for 2.0 release

Author: pcallewaert

README.md

@@ -27,7 +27,9 @@ None
 In order for this operator to work correctly with AWS RDS, you need to set `POSTGRES_CLOUD_PROVIDER` to `AWS` either in
 the ext-postgres-operator kubernetes secret or directly in the deployment manifest (`operator.yaml`).
 
-### Azure Database for PostgreSQL (both Single Server and Flexible Server)
+### Azure Database for PostgreSQL - Flexible Server
+
+> **Note:** Starting from version 2.x, Azure Database for PostgreSQL - Single server is no longer supported, as it has been deprecated by Microsoft. Only Azure Database for PostgreSQL - Flexible Server is supported.
 
 In order for this operator to work correctly with Azure managed PostgreSQL database, two env variables needs to be provided for the operator:
 
@@ -36,7 +38,7 @@ In order for this operator to work correctly with Azure managed PostgreSQL datab
 
 ### GCP
 
-In order for this operator to work correctly with GCP, you need to set `POSTGRES_CLOUD_PROVIDER` to `GCP` 
+In order for this operator to work correctly with GCP, you need to set `POSTGRES_CLOUD_PROVIDER` to `GCP`
 
 To have operator work with GCP properly you have to:
 * use postgresql connection in secret
@@ -49,17 +51,17 @@ DropRole method will check for db owner and will skip master role dropping
 These environment variables are embedded in [deploy/operator.yaml](deploy/operator.yaml), `env` section.
 
 * `WATCH_NAMESPACE` - which namespace to watch. Defaults to empty string for all namespaces
-* `OPERATOR_NAME` - name of the operator, defaults to `ext-postgres-operator` 
+* `OPERATOR_NAME` - name of the operator, defaults to `ext-postgres-operator`
 * `POSTGRES_INSTANCE` - identity of operator, this matched with `postgres.db.movetokube.com/instance` in CRs. Default is empty
 * `KEEP_SECRET_NAME` - use secret name as provided by user (disabled by default)
 
 `POSTGRES_INSTANCE` is only available since version 1.2.0
 
-> While using `KEEP_SECRET_NAME` could be a convenient way to define secrets with predictable and explicit names, 
-> the default logic reduces risk of operator from entering the endless reconcile loop as secret is very unlikely to exist. 
+> While using `KEEP_SECRET_NAME` could be a convenient way to define secrets with predictable and explicit names,
+> the default logic reduces risk of operator from entering the endless reconcile loop as secret is very unlikely to exist.
 >
-> The administrator should ensure that the `SecretName` does not collide with other secrets in the same namespace. 
-> If the secret already exists, the operator will never stop reconciling the CR until either offending secret is deleted 
+> The administrator should ensure that the `SecretName` does not collide with other secrets in the same namespace.
+> If the secret already exists, the operator will never stop reconciling the CR until either offending secret is deleted
 > or CR is deleted or updated with another SecretName
 
 ## Installation
@@ -96,7 +98,7 @@ To install the operator using kustomize, follow the steps below.
     or by using [kustomize](https://github.com/kubernetes-sigs/kustomize) directly\
     `kustomize build deploy/ | apply -f -`
 
-Alternatively you can install operator using Helm Chart located in the 
+Alternatively you can install operator using Helm Chart located in the
 `charts/ext-postgres-operator` subdirectory. Sample installation commands provided below:
 
 ```
@@ -117,7 +119,7 @@ metadata:
   namespace: app
   annotations:
     # OPTIONAL
-    # use this to target which instance of operator should process this CR. See General config 
+    # use this to target which instance of operator should process this CR. See General config
     postgres.db.movetokube.com/instance: POSTGRES_INSTANCE
 spec:
   database: test-db # Name of database created in PostgreSQL
@@ -189,7 +191,7 @@ For more information and an example, see [kubernetes-replicator#pull-based-repli
 
 #### Template Use Case
 
-Users can specify the structure and content of secrets based on their unique requirements using standard 
+Users can specify the structure and content of secrets based on their unique requirements using standard
 [Go templates](https://pkg.go.dev/text/template#hdr-Actions). This flexibility allows for a more tailored approach to
 meeting the specific needs of different applications.
 
@@ -230,4 +232,5 @@ Postgres operator compatibility with Operator SDK version is in the table below
 |---------------------------|----------------------|----------------------|
 | `postgres-operator 0.4.x` | v0.17                |  v1beta1             |
 | `postgres-operator 1.x.x` | v0.18                |  v1                  |
-| `HEAD`                    | v0.18                |  v1                  |
+| `postgres-operator 2.x.x` | v1.39                |  v1                  |
+| `HEAD`                    | v1.39                |  v1                  |