(DOCSP-9768) Update Charts docs to reflect new split horizon access (#321)

Author: zach-carr

source/launch-charts.txt

@@ -30,10 +30,6 @@ You will also need an |service| cluster to visualize data using
 |charts-short|. The steps on this page guide you through creating an
 |service| cluster.
 
-If your |service| cluster is backed by |gcp| or Azure, the cluster
-must not have :atlas:`network peering </security-vpc-peering>` enabled.
-For more information, see :ref:`limited-peering-support`.
-
 .. note::
 
    Each instance of the |charts| application is tied to a single
@@ -58,28 +54,6 @@ on configuring additional users and roles, see
 :atlas:`Atlas Access </tutorial/manage-users/>` in the
 |service| documentation.
 
-.. _limited-peering-support:
-
-Limited Support for Network Peering Connections
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-You cannot enable |charts| if your |service| project contains a cluster
-with |gcp| :abbr:`VPC (Virtual Private Cloud)` or Azure VNet
-:atlas:`network peering </security-vpc-peering>` enabled.
-When network peering is enabled, GCP and Azure block network access
-from outside of the peered network, meaning these projects cannot
-communicate with the MongoDB Stitch backend that powers |charts-short|.
-
-To access |charts| on a project containing a |gcp| or Azure-backed
-cluster with network peering enabled,
-:onprem:`install the on-premises version of MongoDB Charts
-</installation>` on a virtual machine in the VPC or VNet instance.
-
-.. note::
-
-   |charts| is fully supported on |aws| clusters with network peering
-   enabled.
-
 Procedure
 ---------