Skip to content

DOCS-531 Azure Conductor/hub/spoke Deployment guides - #1122

Open
Chr1st0ph3rTurn3r wants to merge 2 commits into
masterfrom
DOCS-531-azure-conductor-deployment-guide
Open

DOCS-531 Azure Conductor/hub/spoke Deployment guides#1122
Chr1st0ph3rTurn3r wants to merge 2 commits into
masterfrom
DOCS-531-azure-conductor-deployment-guide

Conversation

@Chr1st0ph3rTurn3r

Copy link
Copy Markdown
Contributor

No description provided.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds new Azure-focused deployment documentation to the Docusaurus docs site, covering both an Azure conductor deployment and an Azure hub/spoke router topology, and exposes these guides through the sidebar navigation.

Changes:

  • Added Azure Conductor deployment guide set (overview + step-by-step pages + appendix + network design partial).
  • Added Azure Hub-and-Spoke router deployment guide set (overview + step-by-step pages + appendix + network design partial).
  • Updated the Deployment Guides overview page and sidebar to include the new Azure guide categories.

Reviewed changes

Copilot reviewed 16 out of 16 changed files in this pull request and generated 5 comments.

Show a summary per file
File Description
sidebars.js Adds new “Azure Conductor” and “Azure Hub and Spoke Routers” categories and registers all new doc IDs.
docs/deploy_guides_overview.md Updates the overview text to reflect Azure availability for conductor/router deployment guides.
docs/deploy_azure_conductor.mdx New Azure Conductor deployment guide landing page with topology, prerequisites, and guide index.
docs/deploy_azure_conductor_vm.mdx New Step 1 for deploying the conductor VM via Portal/automation.
docs/deploy_azure_conductor_install.mdx New Step 2 for verifying install completion and initial GUI access.
docs/deploy_azure_conductor_config.mdx New Step 3 for authority-level conductor configuration (imports existing partials).
docs/deploy_azure_conductor_router.mdx New Step 4 for deploying/configuring a conductor-managed Azure router (single-router pattern).
docs/deploy_appendix_azure_conductor.mdx New appendix with complete example PCLI config for the Azure conductor + router.
docs/_deploy_azure_conductor_network_design.md New partial defining consistent Azure conductor guide addressing/naming conventions.
docs/deploy_azure_hub_spoke_overview.mdx New Azure hub/spoke router guide landing page with topology, prerequisites, and guide index.
docs/deploy_azure_hub_spoke_hub_vm.mdx New Step 1 for deploying the hub router VM.
docs/deploy_azure_hub_spoke_spoke_vm.mdx New Step 2 for deploying the spoke router VM.
docs/deploy_azure_hub_spoke_vmbus.mdx New Step 3 for verifying install/onboarding and discovering VMBus UUID mappings.
docs/deploy_azure_hub_spoke_config.mdx New Step 4 for conductor GUI configuration of hub/spoke tenants, interfaces, SVR peering, and routing.
docs/deploy_appendix_azure_hub_spoke.mdx New appendix with complete example PCLI config for the hub/spoke topology.
docs/_deploy_azure_hub_spoke_network_design.md New partial defining consistent hub/spoke guide addressing/naming conventions.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +17 to +20
- A VNet where the Conductor will be deployed (`SSR-VNet` in this guide).
- A subnet within that VNet reachable via SSH and HTTPS for administration (`ssr-conductor-subnet`).
- The subnet must be reachable from the WAN interface of every SSR router this conductor will manage.
- A **Managed Identity** assigned the following minimum read permissions:

5. Launch the deployment:

```bash

Launch the deployment:

```bash

Launch the deployment:

```bash

Launch the deployment:

```bash
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants