From b201d6ab81a1cf24eea85de65d0fd83083f98040 Mon Sep 17 00:00:00 2001 From: Janaki Meyyappan Date: Tue, 7 Apr 2026 10:59:46 -0600 Subject: [PATCH] Add docs for autoscaling feature --- .../getting-started/manual-scaling.md | 59 ------------------- content/nginxaas-google/overview.md | 12 ++++ 2 files changed, 12 insertions(+), 59 deletions(-) delete mode 100644 content/nginxaas-google/getting-started/manual-scaling.md diff --git a/content/nginxaas-google/getting-started/manual-scaling.md b/content/nginxaas-google/getting-started/manual-scaling.md deleted file mode 100644 index 045d395c06..0000000000 --- a/content/nginxaas-google/getting-started/manual-scaling.md +++ /dev/null @@ -1,59 +0,0 @@ ---- -title: Scale your deployment -weight: 400 -toc: true -nd-docs: DOCS-000 -url: /nginxaas/google/getting-started/manual-scaling/ -nd-content-type: how-to -nd-product: NGOOGL ---- - -F5 NGINXaaS for Google Cloud (NGINXaaS) supports manual scaling of your deployment, allowing you to adapt to application traffic demands while controlling cost. - -An NGINXaaS deployment can be scaled out to increase the capacity or scaled in to decrease the capacity. Capacity is measured in [NGINX Capacity Units (NCU)](#nginx-capacity-unit-ncu). - -In this document you will learn: - -- What an NGINX Capacity Unit (NCU) is -- How to manually scale your deployment -- What capacity restrictions apply for your plan -- How to monitor capacity usage -- How to estimate the amount of capacity to provision - -## NGINX Capacity Unit (NCU) - -An NGINX Capacity Unit (NCU) quantifies the capacity of an NGINX instance based on the underlying compute resources. This abstraction allows you to specify the desired capacity in NCUs without having to consider the regional hardware differences. - -## Manual scaling - -To update the capacity of your deployment using the console, - -In the NGINXaaS Console, - -1. On the left menu, select **Deployments**. -2. Select the deployment you wish to edit the NCU capacity for. -3. On the **Details** tab, select the **Edit** button on the right to open the Edit Deployment Metadata pane - - Enter the desired value for the **NCU Capacity** under **Scale**. - - Select **Update** to begin the scaling process. - -The status of the deployment will be "Pending" while the deployment's capacity is being changed. Once the requested capacity provisioning is complete, the status will change to "Ready". - - {{< call-out "note" >}}There's no downtime while an NGINXaaS deployment changes capacity.{{< /call-out >}} - -## Connection draining - -During scale-in, some connections older than 60 seconds might be reset. The service automatically handles reconnects, so you don’t need to wait before reconnecting. - -## Capacity restrictions - -The following table outlines constraints on the specified capacity based on the chosen Marketplace plan, including the minimum capacity required for a deployment to be highly available, and the maximum capacity. By default, an NGINXaaS for Google Cloud deployment will be created with a capacity of 20 NCUs. - -{{}} - -| **Marketplace Plan** | **Minimum Capacity (NCUs)** | **Maximum Capacity (NCUs)** | -|------------------------------|-----------------------------|-----------------------------| -| Enterprise plan(s) | 10 | 100 | - -{{}} - -{{< call-out "note" >}}If you have higher capacity needs than the maximum capacity, please [open a request](https://my.f5.com/manage/s/) and specify the Resource ID of your NGINXaaS deployment, the region, and the desired maximum capacity you wish to scale to.{{< /call-out >}} diff --git a/content/nginxaas-google/overview.md b/content/nginxaas-google/overview.md index 7472311438..00ce18d2c3 100644 --- a/content/nginxaas-google/overview.md +++ b/content/nginxaas-google/overview.md @@ -32,6 +32,7 @@ The key capabilities of NGINXaaS for Google Cloud are: {{< img src="nginxaas-google/nginxaas-google-cloud-architecture.svg" alt="Architecture diagram showing how NGINXaaS integrates with Google Cloud. At the top, inside the Google Cloud IaaS layer, NGINX Plus is managed using UI, API, and Terraform, alongside NGINXaaS. Admins connect to this layer. Below, in the Customer VPC, end users connect through Edge Routing to multiple App Servers (labeled App Server 1). NGINX Plus directs traffic to these app servers. The Customer VPC also connects with Google Cloud services such as Secret Manager, Monitoring, and other services. Green arrows show traffic flow from end users through edge routing and NGINX Plus to app servers, while blue arrows show admin access." >}} - The NGINXaaS Console is used to create, update, and delete NGINX configurations, certificates and NGINXaaS deployments +- NGINXaaS automatically adapts to application traffic demands through autoscaling - Each NGINXaaS deployment has dedicated network and compute resources. There is no possibility of noisy neighbor problems or data leakage between deployments - NGINXaaS can route traffic to upstreams even if the upstream servers are located in different geographies. See [Known Issues]({{< ref "/nginxaas-google/known-issues.md" >}}) for any networking restrictions. - NGINXaaS supports request tracing. See the [Application Performance Management with NGINX Variables](https://www.f5.com/company/blog/nginx/application-tracing-nginx-plus) blog to learn more about tracing. @@ -51,6 +52,17 @@ NGINXaaS for Google has a global presence with management requests being served We use Google [Private Service Connect]((https://cloud.google.com/vpc/docs/private-service-connect)) (PSC) to securely connect NGINXaaS to your applications and enable client access to your deployments. A [PSC backend](https://cloud.google.com/vpc/docs/private-service-connect#backends) brings the NGINXaaS deployment into your client network, allowing your application clients to connect seamlessly. A [PSC Interface](https://cloud.google.com/vpc/docs/private-service-connect#interfaces) brings the deployment into your application network, enabling secure connectivity to your applications. This approach gives you full control over traffic flow by leveraging your own networking resources, so you can apply your preferred security controls and ensure a secure deployment environment. +#### Connection draining + +During scaling, some connections older than 60 seconds might be reset. The service automatically handles reconnects, so you don't need to wait before reconnecting. + +### NGINX Capacity Unit (NCU) + +An NGINX Capacity Unit (NCU) quantifies the capacity of an NGINX deployment based on the underlying compute resources. This abstraction allows you to specify the desired capacity in NCUs without having to consider the regional hardware differences. + +You can reserve a minimum capacity for your deployment. The deployment automatically scales up or down based on the traffic demands but also ensures it does not go below the minimum reserved capacity. + + ## Current Limitations We are committed to enhancing NGINXaaS for Google Cloud and welcome your feedback to help shape the future of our service. If there are features you'd like to see prioritized, we encourage you to submit a [support ticket]({{< ref "/nginxaas-google/get-help/support.md" >}}) to share your suggestions.