Merge pull request #3252 from EnterpriseDB/release/2022-10-12

Release: 2022-10-12
EnterpriseDB · Oct 12, 2022 · 9468136 · 9468136
2 parents 2f5b710 + 3185c1b
commit 9468136
Show file tree

Hide file tree

Showing 124 changed files with 2,123 additions and 1,697 deletions.
diff --git a/advocacy_docs/migrating/oracle/index.mdx b/advocacy_docs/migrating/oracle/index.mdx
@@ -1,8 +1,8 @@
 ---
-title: 'Migration Overview'
+title: 'Migration Handbook'
 indexCards: none
 directoryDefaults:
-   product: "Migration Overview"
+   product: "Migration Handbook"
 navigation:
 - "#Migrating your Oracle database"
 - factors_to_consider

diff --git a/biganimal b/biganimal
diff --git a/product_docs/docs/biganimal/release/overview/03a_region_support.mdx b/product_docs/docs/biganimal/release/overview/03a_region_support.mdx
@@ -15,6 +15,7 @@ When using Azure, you can create clusters in the following regions:
   - South East Asia (Singapore)
 - Europe, Middle East, Africa (EMEA)
   - France Central (Paris)
+  - Germany West Central (Frankfurt)
   - North Europe (Ireland)
   - Norway East (Oslo)
   - UK South (London)
@@ -38,6 +39,7 @@ When using Azure, you can create clusters in the following regions:
   - Japan East (Tokyo, Saitama)
   - South East Asia (Singapore)
 - Europe, Middle East, Africa (EMEA)
+  - Germany West Central (Frankfurt)
   - North Europe (Ireland)
   - UK South (London)
 - North America (NA):

diff --git a/...ter/02_connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx b/...ter/02_connecting_your_cluster/01_connecting_from_azure/01_private_endpoint.mdx
diff --git a/...connecting_your_cluster/01_connecting_from_azure/02_virtual_network_peering.mdx b/...connecting_your_cluster/01_connecting_from_azure/02_virtual_network_peering.mdx
@@ -4,6 +4,9 @@ redirects:
  - /biganimal/release/using_cluster/connecting_your_cluster/01_connecting_from_azure/02_virtual_network_peering/
 ---
 
+Virtual network peering connects two Azure Virtual Networks, allowing traffic to be freely routed between the two. Once peered, the two virtual networks act as one with respect to connectivity. Network Security Group rules are still observed. Virtual network peering is simple and easy to set up, but the limitation is that the IP ranges of two peered virtual networks can't overlap. See [pricing for virtual network peering](https://azure.microsoft.com/en-us/pricing/details/virtual-network/#pricing) for the associated cost.
+
+## Example
 This example shows how to connect using virtual network peering. The IP ranges of two peered virtual networks can't overlap. BigAnimal VNets use the 10.240.0.0/14 address space and cannot be peered with VNets using this same space. 
 
 !!! Note

diff --git a/...ng_cluster/02_connecting_your_cluster/01_connecting_from_azure/03_vnet_vnet.mdx b/...ng_cluster/02_connecting_your_cluster/01_connecting_from_azure/03_vnet_vnet.mdx
@@ -4,6 +4,18 @@ redirects:
  - /biganimal/release/using_cluster/connecting_your_cluster/01_connecting_from_azure/03_vnet_vnet/
 ---
 
+VNet-VNet connections use VPN gateways to send encrypted traffic between Azure virtual networks. Advantages include:
+
+-   Cluster domain name is directly accessible without a NAT. 
+-   VNets from different subscriptions don't need to be associated with the same Active Directory tenant.
+
+Cons include:
+
+-   Bandwidth is limited. See [virtual network gateway planning table](https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways#planningtable). 
+-   Configuration is complicated.
+-   There is an associated cost. See [virtual network gateway planning table](https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways#planningtable).
+
+## Example 
 This example shows how to connect using VNet-VNet connections. 
 
 To use this method, you need to create [Azure VPN Gateways](https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways) in each connected virtual network.