Skip to content

Commit 4d57617

Browse files
authored
(DOCSP-9768) Update Charts docs to reflect new split horizon access (#321)
1 parent 4233c97 commit 4d57617

File tree

1 file changed

+0
-26
lines changed

1 file changed

+0
-26
lines changed

source/launch-charts.txt

Lines changed: 0 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -30,10 +30,6 @@ You will also need an |service| cluster to visualize data using
3030
|charts-short|. The steps on this page guide you through creating an
3131
|service| cluster.
3232

33-
If your |service| cluster is backed by |gcp| or Azure, the cluster
34-
must not have :atlas:`network peering </security-vpc-peering>` enabled.
35-
For more information, see :ref:`limited-peering-support`.
36-
3733
.. note::
3834

3935
Each instance of the |charts| application is tied to a single
@@ -58,28 +54,6 @@ on configuring additional users and roles, see
5854
:atlas:`Atlas Access </tutorial/manage-users/>` in the
5955
|service| documentation.
6056

61-
.. _limited-peering-support:
62-
63-
Limited Support for Network Peering Connections
64-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
65-
66-
You cannot enable |charts| if your |service| project contains a cluster
67-
with |gcp| :abbr:`VPC (Virtual Private Cloud)` or Azure VNet
68-
:atlas:`network peering </security-vpc-peering>` enabled.
69-
When network peering is enabled, GCP and Azure block network access
70-
from outside of the peered network, meaning these projects cannot
71-
communicate with the MongoDB Stitch backend that powers |charts-short|.
72-
73-
To access |charts| on a project containing a |gcp| or Azure-backed
74-
cluster with network peering enabled,
75-
:onprem:`install the on-premises version of MongoDB Charts
76-
</installation>` on a virtual machine in the VPC or VNet instance.
77-
78-
.. note::
79-
80-
|charts| is fully supported on |aws| clusters with network peering
81-
enabled.
82-
8357
Procedure
8458
---------
8559

0 commit comments

Comments
 (0)