⚠ This page is served via a proxy. Original site: https://github.com
This service does not collect credentials or authentication data.
Skip to content

Conversation

@Naveen-Gopu-F5
Copy link
Contributor

Proposed changes

  • Included the steps/documentation about the vmss backend which helps in dynamic update of upstreams in NGINXaaS

Checklist

Before sharing this pull request, I completed the following checklist:

Footnotes

  1. Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content.

@github-actions github-actions bot added documentation Improvements or additions to documentation product/nginxaas-azure Issues related to NGINX as a Service for Azure labels Jan 8, 2026
@github-actions
Copy link

github-actions bot commented Jan 8, 2026

Deploy Preview will be available once build job completes!

Name Link
😎 Deploy Preview https://frontdoor-test-docs.nginx.com/previews/docs/1642/

@Naveen-Gopu-F5 Naveen-Gopu-F5 requested a review from ryepup January 8, 2026 17:40
Copy link
Contributor

@arussellf5 arussellf5 left a comment

Choose a reason for hiding this comment

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

This is excellent documentation! Thank you


## Getting Started

### Step 1: Create NGINXaaS deployment with dynamic upstreams
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
### Step 1: Create NGINXaaS deployment with dynamic upstreams
### Create NGINXaaS deployment with dynamic upstreams

Copy link
Contributor

Choose a reason for hiding this comment

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

Make this at other places as well.
Refer: #1384

Copy link
Contributor Author

Choose a reason for hiding this comment

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

updated above suggested changes


## Overview

The NGINXaaS dataplane API key is used to authenticate with your NGINXaaS deployment's dataplane API. This key is required for various integrations including VMSS backend synchronization and Kubernetes load balancing.
Copy link
Contributor

Choose a reason for hiding this comment

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

Arent these both load balancing (VMSS and Kubernetes)?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, it is useful both. Thats the reason i created a separate common page and use this reference in both VMSS and kubernetes places

Copy link
Contributor

Choose a reason for hiding this comment

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

So maybe just call it VMSS load balancing (@arussellf5 what do you think?).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

updated to VMSS load balancing

@Naveen-Gopu-F5 Naveen-Gopu-F5 marked this pull request as ready for review January 13, 2026 17:53
@Naveen-Gopu-F5 Naveen-Gopu-F5 requested review from a team as code owners January 13, 2026 17:53

```bash
# Set role name
roleName="VMSS-Network-Read-Role"
Copy link
Contributor

@russokj russokj Jan 15, 2026

Choose a reason for hiding this comment

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

Why set this here? It's not used until later (in the Assign the Custom Role script).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Nice catch, shifted it to Assign the Custom Role section

```yaml
# nginx-asg-sync configuration for NGINXaaS for Azure
cloud_provider: Azure
subscription_id: your_subscription_id
Copy link
Contributor

Choose a reason for hiding this comment

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

In the json file mentioned above, you used "<SUBSCRIPTION_ID>" nomenclature to indicate items that the user needed to substitute real values into. Should we use the same pattern here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

updated to <SUBSCRIPTION_ID>


```
2026/01/08 15:44:12 nginx-asg-sync version 1.0.3
2026/01/08 15:44:13 Updated HTTP servers of backend-one for group naveen-vmss-latest ; Added: [172.19.0.6:80 172.19.0.7:80], Removed: [], Updated: []
Copy link
Contributor

Choose a reason for hiding this comment

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

Probably don't want your name in here (and below)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Removed names and used backend-one


You can assign managed identity permissions using:

- **Azure Portal**: Navigate to **Resource** → **Identity** → **Role assignments** in the Azure portal
Copy link
Contributor

Choose a reason for hiding this comment

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

Wasn't clear what the starting point for this was? Which resource should I be looking at in the Portal?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, updated to specific resource like vm, vmss

@@ -0,0 +1,485 @@
---
title: Virtual Machine Scale Sets (VMSS) Backend Integration
Copy link
Contributor

Choose a reason for hiding this comment

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

We call this file vmss-backend.md but for kubernetes we call it loadbalancer-kubernetes.md. I'm wondering, for consistency sake, we call this loadbalancer-vmss.md instead. I'd also change the title to be consistent too. (@arussellf5 please input if you think differently).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

updated the title and file names as suggested to main consistency

Before setting up VMSS backend integration, ensure you have:

- An active NGINXaaS for Azure deployment
- Azure Virtual Machine Scale Sets (VMSS)
Copy link
Contributor

Choose a reason for hiding this comment

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

Please highlight that the orchestration mode must be set to uniform and not flexible.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Highlighted as suggested above

proxy_pass http://backend-two;
}

location @hc-backend-two {
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need to have two backend upstream groups. Seems for simplicity we'd just keep this simple and create one upstream group.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

simplified it by including only one upstream group

Copy link
Contributor

@russokj russokj left a comment

Choose a reason for hiding this comment

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

No major issues. Just come suggestions.

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

Labels

documentation Improvements or additions to documentation product/nginxaas-azure Issues related to NGINX as a Service for Azure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants