Merge pull request #2668 from EnterpriseDB/release/2022-05-13

Release: 2022-05-13

product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx

@@ -58,6 +58,8 @@ Prior to creating your cluster, make sure you have enough resources. Without eno
 6.  In the **Networking Connectivity** section, you specify whether to use private or public networking. Networking is set to **Public** by default. Public means that any client can connect to your cluster’s public IP address over the internet. Optionally, you can limit traffic to your public cluster by specifying an IP allowlist, which allows access only to certain blocks of IP addresses. To limit access, add one or more classless inter-domain routing (CIDR) blocks in the **IP Allowlists** section. CIDR is a method for allocating IP addresses and IP routing to a whole network or subnet. If you have any CIDR block entries, access is limited to those IP addresses. If none are specified, all network traffic is allowed. 
 
     Private networking allows only IP addresses within your private network to connect to your cluster. See [Cluster networking architecture](01_cluster_networking) for more information.
+
+
 7.  To optionally make updates to your database configuration parameters, select **Next: DB Configuration**.
 
 ### DB Configuration tab

product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx

@@ -21,6 +21,7 @@ Assume that your cluster is on a subscription called `development` and is being
     -   Virtual network: `vnet-client`
     -   Virtual network subnet: `snet-client`
 
+
 #### Prerequisites
 
 To walk through an example in your own environment, you need:

product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/index.mdx

@@ -12,8 +12,12 @@ Three different methods enable you to connect to your cluster from your applicat
 
 ## Azure Private Endpoint (recommended)
 
- Azure Private Endpoint is a network interface that securely connects a private IP 
- address from your Azure Virtual Network (VNet) to an external service. You grant access only to a single cluster instead of the entire BigAnimal resource virtual network, thus ensuring maximum network isolation. Private Endpoints are the same mechanism used by first-party Azure services such as CosmosDB for private VNet connectivity. For more information, see [What is an Azure Private Endpoint?](https://docs.microsoft.com/en-us/azure/private-link/private-endpoint-overview).
+Azure Private Endpoint is a network interface that securely connects a private IP 
+address from your Azure Virtual Network (VNet) to an external service. You grant access only to a single cluster instead of the entire BigAnimal resource virtual network, thus ensuring maximum network isolation. Private Endpoints are the same mechanism used by first-party Azure services such as CosmosDB for private VNet connectivity. For more information, see [What is an Azure Private Endpoint?](https://docs.microsoft.com/en-us/azure/private-link/private-endpoint-overview).
+
+!!!note
+If you setup a private endpoint and want to change to a public network, you must remove the private endpoint resources before making the change.
+!!!
 
 **Pros**
 

product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/index.mdx

@@ -56,7 +56,7 @@ SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, bits: 256, co
 
 The Private Networking option offers a higher level of isolation and security by moving your cluster out of the public Internet. Clusters with Private Networking enabled are by default not accessible from outside of your cluster's resource network. You need to perform additional configuration steps to connect your applications in other parts of your cloud infrastructure to your clusters via private network links.
 
-!!! Note
+!!!note
     EDB strongly discourages provisioning additional resources in the cluster's resource virtual network.
 
 For examples to guide you through the different methods of connecting to your cluster, see 

product_docs/docs/biganimal/release/using_cluster/03_modifying_your_cluster/index.mdx

@@ -27,11 +27,13 @@ You can modify your cluster by modifying:
     | ----------------------------------- | ----------------------------------------------------------------------------------------- |
     | Cluster name and password           | [Cluster Settings](../../getting_started/03_create_cluster/#cluster-settings-tab)                 |
     | Instance type \*  | [Cluster Settings](../../getting_started/03_create_cluster/#cluster-settings-tab) |
-    | Networking type (public or private) | [Cluster Settings](../../getting_started/03_create_cluster/#cluster-settings-tab)|
+    | Networking type (public or private) \**| [Cluster Settings](../../getting_started/03_create_cluster/#cluster-settings-tab)|
     | Database configuration parameters   | [DB Configuration](05_db_configuration_parameters)                       |
     | High availability (on or off)       | [Availability](../../getting_started/03_create_cluster/#availability-tab)                 |
 
-    \*Changing the instance type could incur higher cloud infrastructure charges.
+    \* Changing the instance type could incur higher cloud infrastructure charges.
+
+    \** If you are using Azure and previously setup a private link and want to change to a public network, you must remove the private link resources before making the change.
 
     !!! Note
         Saving changes might require a database restart.

product_docs/docs/efm/4/12_upgrading_existing_cluster.mdx

@@ -62,6 +62,9 @@ If you're [using a Failover Manager configuration without sudo](04_configuring_e
 
 ## Uninstalling Failover Manager
 
+!!! Note
+    If you are using custom scripts, check to see if they are calling any Failover Manager scripts. For example, a script that runs after promotion to perform various tasks and then calls Failover Manager's `efm_address` script to acquire a virtual IP address. If you have any custom scripts calling Failover Manager scripts, update the custom scripts to use the newly installed version of the Failover Manager script before uninstalling the older version of the Failover Manager script.
+
 After upgrading to Failover Manager 4.4, you can use your native package manager to remove previous installations of Failover Manager. For example, use the following command to remove Failover Manager 4.1 and any unneeded dependencies:
 
 -   On RHEL or CentOS 7.x: