Issue Summary

The Mesh FAQs here currently state that the deployment of Mesh on multiple Availability Zones (AZs) is not supported. This information is outdated and needs to be updated to reflect the current support status. Additionally, the BSERV link associated with the question "Can I deploy Mesh nodes in different locations or availability zones?" is incorrect and should be updated to BSERV-13270.

Can I deploy Mesh nodes in different locations or availability zones?
Currently, we will not be supporting deploying Mesh nodes into multiple availability zones. Just like the shared file system-based deployments, the Mesh nodes (that is, the repository storage) and the application nodes must be co-located. We are exploring the ability to support the deployment of Mesh nodes to multiple Availability Zones in BSERV-13269 - Mesh: Migration of LFS objects to Mesh Gathering Interest

Steps to Reproduce

1. Visit the Mesh FAQs page here.
2. Locate the section titled "Can I deploy Mesh nodes in different locations or availability zones?"

Expected Results

The FAQ should indicate that deploying Mesh nodes on multiple Availability Zones is supported, and the link should point to the correct BSERV BSERV-13270: Mesh: Support Mesh nodes being deployed to multiple Availability Zones (fixed in Bitbucket Data Center 9.3.0).

Actual Results

The FAQ incorrectly states that deployment on multiple Availability Zones is not supported, and the link points to an incorrect BSERV issue.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available.