[DOCS-15143] [Atlas] GCP Private Service Connect confusion in Docs Created: 03/Mar/22 Updated: 29/Oct/23 Resolved: 08/Mar/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Atlas |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Trivial - P5 |
| Reporter: | Philipp Waffler | Assignee: | Kanchana Sekhar |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | cet-captain | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 48 weeks, 1 day ago |
| Story Points: | 1 |
| Description |
|
In our documentation one of our customers was confused by the considerations for the GCP PSC: https://docs.atlas.mongodb.com/security-private-endpoint/#regionalized-private-endpoints-for-multi-region-sharded-clusters They thought it would be mandatory that a GCP PSC could only be set up for multi-region sharded cluster. I think adding an "optional" to the headline of the subsection could reduce the number of confused customers at this point. |
| Comments |
| Comment by Kanchana Sekhar [ 08/Mar/22 ] |
|
Merged PR to master |
| Comment by Philipp Waffler [ 03/Mar/22 ] |