NLB-7247: Update changelog with v3 plan and plan migration #1476
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
documentation
✅ Deploy Preview will be available once build job completes!
|
arpith-f5
reviewed
Nov 24, 2025
|
|
||
| To review older entries, visit the [Changelog archive]({{< ref "/nginxaas-azure/changelog/archive" >}}) section. | ||
|
|
||
| ## December 13, 2025 |
|
Proposal looks good to me |
russokj
reviewed
Nov 25, 2025
|
|
||
| F5 NGINXaaS for Azure (NGINXaaS) now supports in-place migration from Standard V2 plan to the Standard V3 plan, we encourage you to upgrade your deployment to the Standard V3 plan as soon as possible. **The Standard V2 plan is scheduled for retirement on Feb 1, 2026**. If you fail to migrate by Feb 1, 2026, your NGINXaaS deployment will stop receiving automatic updates that address critical security issues. | ||
|
|
||
| The Standard V3 plan is an upgraded, purpose-built solution for modern enterprises looking to simplify application traffic management and scale workloads effortlessly. The Standard V3 pricing model is designed to optimize efficiency and transparency: customers benefit from an affordable fixed price per deployment ($0.25/hour) that covers baseline overhead, while NCU usage ($0.008/hour/unit) and data processing ($0.005/GB) allow costs to scale precisely with demand. |
Contributor
There was a problem hiding this comment.
Not sure how we optimize transparency. Maybe look at what we said for V2 and use that.
Contributor
Author
There was a problem hiding this comment.
Not sure how we optimize transparency. Maybe look at what we said for V2 and use that.
just took this language/sentence from this confluence doc. In v2 plan we just added introducing of waf and additional port .
russokj
reviewed
Nov 25, 2025
|
|
||
| The Standard V3 plan is an upgraded, purpose-built solution for modern enterprises looking to simplify application traffic management and scale workloads effortlessly. The Standard V3 pricing model is designed to optimize efficiency and transparency: customers benefit from an affordable fixed price per deployment ($0.25/hour) that covers baseline overhead, while NCU usage ($0.008/hour/unit) and data processing ($0.005/GB) allow costs to scale precisely with demand. | ||
|
|
||
| {{< call-out "note" >}} We currently only support in-place migration from Standard V2 plan to the Standard V3 plan and from Standard to Standard V3 plan. Please avoid updating your Basic plan deployments to Standard V3 plan using this guide. {{< /call-out >}} |
Contributor
There was a problem hiding this comment.
I don't think it is possible to migrate from basic to v3, so maybe replace 'Please avoid updating' to something like 'You cannot update'.
Contributor
Author
There was a problem hiding this comment.
updated to You cannot update your Basic plan deployments to Standard V3 plan using this guide.
…s for standardv3 plan
…s for standardv3 plan
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
standardv3planstandardv2tostandardv3Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩