generated from nginx/template-repository
-
Notifications
You must be signed in to change notification settings - Fork 134
NLB-7247: Update changelog with v3 plan and plan migration #1476
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Naveen-Gopu-F5
wants to merge
5
commits into
main
Choose a base branch
from
NLB-7247-update-plan-migration-for-v3-plan
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
12807cb
NLB-7247: Update changelog with v3 plan and plan migration
Naveen-Gopu-F5 5e57bd6
NLB-7247: Update changelog with migration plan and add migration step…
Naveen-Gopu-F5 2381aff
NLB-7247: Update changelog with migration plan and add migration step…
Naveen-Gopu-F5 e0141c1
Apply suggestions from code review
Naveen-Gopu-F5 414cdf1
NLB-7247: Add generic plan migrations
Naveen-Gopu-F5 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
69 changes: 69 additions & 0 deletions
69
content/nginxaas-azure/billing/change-plan/migrate-from-standardv2.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,69 @@ | ||
| --- | ||
| title: Migrate to new pricing plans | ||
| weight: 100 | ||
| toc: true | ||
| url: /nginxaas/azure/billing/change-plan/migrate-between-plans/ | ||
| type: | ||
| - how-to | ||
| --- | ||
|
|
||
| ## Overview | ||
|
|
||
| F5 NGINXaaS for Azure (NGINXaaS) supports in-place migration between certain pricing plans without requiring redeployment. This allows you to upgrade your deployment to access new features and capabilities while maintaining your existing configuration and avoiding downtime. | ||
|
|
||
| ## Supported migration paths | ||
|
|
||
| The following in-place migrations are supported: | ||
|
|
||
| - **Basic → Developer**: Upgrade from the Basic plan to the Developer plan to access advanced features | ||
| - **Standard → Standard V3**: Upgrade from the legacy Standard plan to the modern Standard V3 plan | ||
| - **Standard V2 → Standard V3**: Upgrade from Standard V2 to Standard V3 to access the latest features and pricing model | ||
|
|
||
| {{< call-out "important" >}} | ||
| If you have a Standard or Standard V2 plan deployment, we encourage you to migrate to the Standard V3 plan as soon as possible. If you have a Basic plan deployment, we encourage you to migrate to the Developer plan as soon as possible. Legacy plans will stop receiving automatic updates that address critical security issues. | ||
| {{< /call-out >}} | ||
|
|
||
| ## Migration steps | ||
|
|
||
| ### Use the Azure portal | ||
|
|
||
| 1. Go to the **Overview** page of the NGINXaaS deployment in the Azure portal. | ||
| 2. Under **Essentials**, find the **Pricing Tier** and select **Click to Upgrade**. | ||
| 3. Select the target plan you want to migrate to and select **Submit**. | ||
|
|
||
| ### Use Terraform | ||
|
|
||
| 1. Update the Terraform AzureRM provider to 4.6.0 or above. | ||
|
|
||
| ``` | ||
| terraform { | ||
| required_version = "~> 1.3" | ||
| required_providers { | ||
| azurerm = { | ||
| source = "hashicorp/azurerm" | ||
| version = "~> 4.6.0" | ||
| } | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| 2. Modify the SKU in the `azurerm_nginx_deployment` resource to your target plan: | ||
| - For Developer plan: `developer_Monthly` | ||
| - For Standard V3 plan: `standardv3_Monthly` | ||
|
|
||
| 3. Run `terraform plan` and review the output to ensure your NGINXaaS deployment is being updated (not replaced). | ||
| 4. Run `terraform apply` to complete the migration. | ||
|
|
||
| ### Use the Azure CLI | ||
|
|
||
| Run the command below to update your NGINXaaS deployment, replacing the SKU name with your target plan: | ||
|
|
||
| ```shell | ||
| az nginx deployment update --name myDeployment --resource-group myResourceGroup \ | ||
| --sku name="<target_sku_name>" | ||
| ``` | ||
|
|
||
| Replace `<target_sku_name>` with one of the following: | ||
|
|
||
| - `developer_n7ja87drquhy` for Developer plan | ||
| - `standardv3_Monthly_n7ja87drquhy` for Standard V3 plan | ||
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's called 'Pricing Plan'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.