Merge pull request #484 from AviatrixDev/sk-avx-22306

Update Cluster_Peering_Ref_Design.rst

HowTos/Cluster_Peering_Ref_Design.rst

@@ -3,21 +3,19 @@
    :keywords: cluster, peering, cluster peering, Aviatrix, AWS VPC, Egress control
 
 =====================================
-Cluster Peering
+Cluster Peering 
 =====================================
 
+.. note::
+
+   The Cluster Peering feature is deprecated.
 
 
 Performance Challenges
 ==============================
 
-<<<<<<< Updated upstream
 Today, encrypted peering (IPsec tunnel) between two VPC/VNets is carried out
-by two gateways (virtual machine, or instance based), one in each VPC/VNet. This limits IPsec
-=======
-Today encrypted peering (an IPsec tunnel) between two VPCs is carried out
-by two gateways (EC2 instance based), one in each VPC. This limits IPSEC
->>>>>>> Stashed changes
+by two gateways (virtual machine, or instance based), one in each VPC/VNet. This limits IPsec Stashed changes
 tunnel packet throughput to the throughput of a single instance. For
 example, AWS C4.4xlarge provides up to 1.5Gbps for an iperf test with
 TCP. There is no solution for use cases that require more than that