Merge pull request #2109 from EnterpriseDB/2021-12-07

Release: 2021-12-07
EnterpriseDB · Dec 7, 2021 · 8414b65 · 8414b65
2 parents 0aacfc7 + 28d3fc7
commit 8414b65
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 5 deletions.
diff --git a/docs/agreements/doc-release-tag-format.md b/docs/agreements/doc-release-tag-format.md
@@ -7,8 +7,9 @@
 | EDB Cloud                    | edbcloud                                                | product/edbcloud/*version*         | Aislinn Wright |
 | EDB Postgres Advanced Server | epas                                                    | product/epas/*version*             | Robert Haas |
 | Failover Manager             | efm                                                     | product/efm/*version*              | John Dalton, Robert Bissett (Bobby) |
-| Foriegn Data Wrappers        | *name*-fdw, where *name* is hadoop, mongo, or mysql       | product/*name*-fdw/*version*      | Jeevan Chalke |
+| Foriegn Data Wrappers        | *name*-fdw, where *name* is hadoop, mongo, or mysql     | product/*name*-fdw/*version*       | Jeevan Chalke |
 | HARP                         | harp                                                    | product/harp/*version*             | John Dalton |
+| LiveCompare                  | livecompare                                             | product/livecompare/*version*      | |
 | Migration Portal             | mp                                                      | product/mp/*version*               | Prashant Argawal |
 | Migration Toolkit            | mtk                                                     | product/mtk/*version*              | Prashant Argawal 
 | Postgres Enterprise Manager  | pem                                                     | product/pem/*version*              | Anthony Waite, Ashesh Vashi |

diff --git a/.../biganimal/release/getting_started/creating_a_cluster/01_cluster_networking.mdx b/.../biganimal/release/getting_started/creating_a_cluster/01_cluster_networking.mdx
@@ -40,7 +40,7 @@ networking configuration for your cluster.
 
 This IP address is private to the VNet hosting your BigAnimal
 services. By default it is not routable from other networks, even in
-your Azure account. See [Setting up Azure infrastructure to connect to a private network cluster](../../using_cluster/connecting_your_cluster/#setting-up-azure-infrastructure-to-connect-to-a-private-network-cluster) for details and instructions
+your Azure account. See [Setting up Azure infrastructure to connect to a private network cluster](../../using_cluster/02_connecting_your_cluster/#setting-up-azure-infrastructure-to-connect-to-a-private-network-cluster) for details and instructions
 on how to properly configure routing for private clusters.
 
 Only one Azure Internal Load Balancer per BigAnimal region is typically deployed in your

diff --git a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx
@@ -49,9 +49,12 @@ Prior to creating your cluster, make sure you have adequate Azure resources or y
 5. In the **Storage** section, select **Volume Type**. In **Volume Properties**, select the type and amount of storage needed for your cluster.
    !!! Note
        BigAnimal currently supports Azure Premium SSD storage types. See [the Azure documentation](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types#premium-ssds) for more information.
-6. In the **Networking** section, 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. 
-Private networking allows only IP addresses in your private network to connect to your cluster. See [Cluster networking architecture](01_cluster_networking) for more information.
-7. To make any updates to your database configuration parameters, select **Next: DB Configuration**.
+6. In the **Networking** 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 only allows access 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
 In the **Parameters** section, you can update the value of the database configuration parameters, as needed.