Skip to content

Add docs for autoscaling feature#1836

Open
janakimeyyappan wants to merge 1 commit intomainfrom
autoscaling_doc
Open

Add docs for autoscaling feature#1836
janakimeyyappan wants to merge 1 commit intomainfrom
autoscaling_doc

Conversation

@janakimeyyappan
Copy link
Copy Markdown
Contributor

Add documentation for autoscaling feature in NGINXaaS for GCP

@janakimeyyappan janakimeyyappan requested a review from a team as a code owner April 7, 2026 17:11
@github-actions github-actions bot added the documentation Improvements or additions to documentation label Apr 7, 2026
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 7, 2026

Deploy Preview will be available once build job completes!

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

@JTorreG
Copy link
Copy Markdown
Contributor

JTorreG commented Apr 7, 2026

@janakimeyyappan can you review the current template for how-tos and make sure your new document is following the guidance? https://github.com/nginx/documentation/tree/main/templates/how-to

Then let us know to start the review.

Comment on lines +11 to +13
F5 NGINXaaS for Google Cloud (NGINXaaS) supports autoscaling of your deployment, automatically adapting to application traffic demands.

An NGINXaaS deployment automatically adjusts capacity based on traffic patterns. Capacity is measured in [NGINX Capacity Units (NCU)](#nginx-capacity-unit-ncu).
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I think we take out "supports autoscaling" and bring these down to:

Suggested change
F5 NGINXaaS for Google Cloud (NGINXaaS) supports autoscaling of your deployment, automatically adapting to application traffic demands.
An NGINXaaS deployment automatically adjusts capacity based on traffic patterns. Capacity is measured in [NGINX Capacity Units (NCU)](#nginx-capacity-unit-ncu).
F5 NGINXaaS for Google Cloud (NGINXaaS) automatically adapts to application traffic demands.
If you want to reserve capacity ahead of time to be even more resilient to sudden spikes you can specify how many [NGINX Capacity Units (NCU)](#nginx-capacity-unit-ncu) to always have available.

@janakimeyyappan janakimeyyappan requested a review from a team as a code owner April 8, 2026 19:46
@janakimeyyappan
Copy link
Copy Markdown
Contributor Author

@janakimeyyappan can you review the current template for how-tos and make sure your new document is following the guidance? https://github.com/nginx/documentation/tree/main/templates/how-to

Then let us know to start the review.

@JTorreG per offline discussion we are removing this page and adding info about this feature to existing pages.

@JTorreG JTorreG requested a review from a team April 9, 2026 16:55

#### 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.
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.

Is this true for scale up or just scale down? Not sure if this is important enough to distinguish, but just throwing the question out there.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants