Conversation
✅ Deploy Preview will be available once build job completes!
|
|
@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. |
| 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). |
There was a problem hiding this comment.
I think we take out "supports autoscaling" and bring these down to:
| 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. |
9e44e9e to
b201d6a
Compare
@JTorreG per offline discussion we are removing this page and adding info about this feature to existing pages. |
|
|
||
| #### 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. |
There was a problem hiding this comment.
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.
Add documentation for autoscaling feature in NGINXaaS for GCP