@@ -30,10 +30,6 @@ You will also need an |service| cluster to visualize data using
30
30
|charts-short|. The steps on this page guide you through creating an
31
31
|service| cluster.
32
32
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
-
37
33
.. note::
38
34
39
35
Each instance of the |charts| application is tied to a single
@@ -58,28 +54,6 @@ on configuring additional users and roles, see
58
54
:atlas:`Atlas Access </tutorial/manage-users/>` in the
59
55
|service| documentation.
60
56
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
-
83
57
Procedure
84
58
---------
85
59
0 commit comments