Merge pull request #241618 from leonard520/app1000

denrea · web-flow · commit 0f5b214d6e89 · 2023-07-05T14:44:47.000-07:00
add description for support 1000 app instances in Enterprise plan
diff --git a/articles/spring-apps/how-to-configure-enterprise-spring-cloud-gateway.md b/articles/spring-apps/how-to-configure-enterprise-spring-cloud-gateway.md
@@ -262,15 +262,15 @@ req.send();
 
 Cross-origin resource sharing (CORS) allows restricted resources on a web page to be requested from another domain outside the domain from which the first resource was served. The available CORS configuration options are described in the following table.
 
-| Property                | Description                                                                       |
-|-------------------------|-----------------------------------------------------------------------------------|
-| `allowedOrigins`        | Allowed origins to make cross-site requests.                                      |
-| `allowedOriginPatterns` | Allowed origin patterns to make cross-site requests.                              |
-| `allowedMethods`        | Allowed HTTP methods on cross-site requests.                                      |
-| `allowedHeaders`        | Allowed headers in cross-site request.                                            |
-| `maxAge`                | How long, in seconds, the response from a preflight request is cached by clients. |
-| `allowCredentials`      | Whether user credentials are supported on cross-site requests.                    |
-| `exposedHeaders`        | HTTP response headers to expose for cross-site requests.                          |
+| Property                | Description                                                                |
+|-------------------------|----------------------------------------------------------------------------|
+| `allowedOrigins`        | Allowed origins to make cross-site requests.                               |
+| `allowedOriginPatterns` | Allowed origin patterns to make cross-site requests.                       |
+| `allowedMethods`        | Allowed HTTP methods on cross-site requests.                               |
+| `allowedHeaders`        | Allowed headers in cross-site request.                                     |
+| `maxAge`                | How long, in seconds, clients cache the response from a preflight request. |
+| `allowCredentials`      | Whether user credentials are supported on cross-site requests.             |
+| `exposedHeaders`        | HTTP response headers to expose for cross-site requests.                   |
 
 > [!NOTE]
 > Be sure you have the correct CORS configuration if you want to integrate with API portal. For more information, see the [Configure Spring Cloud Gateway](#configure-spring-cloud-gateway) section.
@@ -387,41 +387,40 @@ az spring gateway restart \
 
 ---
 
-### Set up Autoscale settings for VMware Spring Cloud Gateway in Azure CLI
+### Set up autoscale settings for VMware Spring Cloud Gateway in Azure CLI
 
-You can set Autoscale modes using the Azure CLI. The following commands create an Autoscale setting and an Autoscale rule.
+You can set autoscale modes using the Azure CLI. The following commands create an autoscale setting and an autoscale rule.
 
-* Create Autoscale setting:
+- Use the following command to create an autoscale setting:
 
-   ```azurecli
-   az monitor autoscale create \
-       --resource-group <resource-group-name> \
-       --name <autoscale-setting-name> \
-       --resource /subscriptions/<subscription-id>/resourcegroups/<resource-group-name>/providers/Microsoft.AppPlatform/Spring/<service-instance-name>/gateways/default \
-       --min-count 1 \
-       --max-count 5 \
-       --count 1
-   ```
+  ```azurecli
+  az monitor autoscale create \
+      --resource-group <resource-group-name> \
+      --name <autoscale-setting-name> \
+      --resource /subscriptions/<subscription-id>/resourcegroups/<resource-group-name>/providers/Microsoft.AppPlatform/Spring/<service-instance-name>/gateways/default \
+      --min-count 1 \
+      --max-count 5 \
+      --count 1
+  ```
 
-* Create Autoscale rule:
+- Use the following command to create an autoscale rule:
 
-   ```azurecli
-   az monitor autoscale rule create \
-       --resource-group <resource-group-name> \
-       --autoscale-name <autoscale-setting-name> \
-       --scale out 1 \
-       --cooldown 1 \
-       --condition "GatewayHttpServerRequestsSecondsCount > 100 avg 1m"
-   ```
+  ```azurecli
+  az monitor autoscale rule create \
+      --resource-group <resource-group-name> \
+      --autoscale-name <autoscale-setting-name> \
+      --scale out 1 \
+      --cooldown 1 \
+      --condition "GatewayHttpServerRequestsSecondsCount > 100 avg 1m"
+  ```
 
 For information on the available metrics, see the [User metrics options](./concept-metrics.md#user-metrics-options) section of [Metrics for Azure Spring Apps](./concept-metrics.md).
 
-
 ---
 
 ## Configure environment variables
 
-Spring Cloud Gateway is managed and tuned by the Azure Spring Apps service. Except for the use cases that configure application performance monitoring and the log level, you don't normally need to configure it with environment variables. But if you do have requirements that you can't fulfill by other configurations described in this article, you can try to configure the environment variables shown in the [Common application properties](https://cloud.spring.io/spring-cloud-gateway/reference/html/appendix.html#common-application-properties) list. Be sure to verify your configuration in your test environment before applying it to your production environment.
+The Azure Spring Apps service manages and tunes Spring Cloud Gateway. Except for the use cases that configure application performance monitoring and the log level, you don't normally need to configure it with environment variables. But if you do have requirements that you can't fulfill by other configurations described in this article, you can try to configure the environment variables shown in the [Common application properties](https://cloud.spring.io/spring-cloud-gateway/reference/html/appendix.html#common-application-properties) list. Be sure to verify your configuration in your test environment before applying it to your production environment.
 
 #### [Azure portal](#tab/Azure-portal)
 
@@ -523,8 +522,8 @@ You can configure the log levels of Spring Cloud Gateway in the following ways t
 - The default log level for Spring Cloud Gateway is `INFO`.
 - You can set log levels to `TRACE`, `DEBUG`, `INFO`, `WARN`, `ERROR`, `OFF`.
 - You can turn off logs by setting log levels to `OFF`.
-- When log levels are set to `WARN`, `ERROR`, `OFF`, you may be required to adjust it to `INFO` when requesting support from the Azure Spring Apps team. This change will cause a restart of Spring Cloud Gateway.
-- When log levels are set to `TRACE` or `DEBUG`, it may impact the performance of Spring Cloud Gateway. Try avoid these settings in your production environment.
+- When log levels are set to `WARN`, `ERROR`, `OFF`, you may be required to adjust it to `INFO` when requesting support from the Azure Spring Apps team. This change causes a restart of Spring Cloud Gateway.
+- When log levels are set to `TRACE` or `DEBUG`, it may affect the performance of Spring Cloud Gateway. Try avoid these settings in your production environment.
 - You can set log levels for the `root` logger or specific loggers like `io.pivotal.spring.cloud.gateway`.
 
 The following loggers may contain valuable troubleshooting information at the `TRACE` and `DEBUG` levels:
@@ -575,7 +574,7 @@ If the log level is sensitive information in your case, you can include it by us
 
 The addon configuration feature enables you to customize certain properties of Spring Cloud Gateway using a JSON format string. The feature is useful when you need to configure properties that aren't exposed through the REST API.
 
-The addon configuration is a JSON object with key-value paris representing the desired configuration. The following example shows the structure of the JSON format:
+The addon configuration is a JSON object with key-value pairs representing the desired configuration. The following example shows the structure of the JSON format:
 
 ```json
 {
diff --git a/articles/spring-apps/how-to-enterprise-deploy-app-at-scale.md b/articles/spring-apps/how-to-enterprise-deploy-app-at-scale.md
@@ -0,0 +1,65 @@
+---
+title: Scale out to deploy over 500 and up to 1000 application instances using Azure Spring Apps Enterprise
+description: Learn how to deploy applications at scale in the Enterprise plan for Azure Spring Apps and learn about the restrictions.
+author: karlerickson
+ms.author: xiading
+ms.service: spring-apps
+ms.topic: how-to
+ms.date: 07/05/2023
+---
+
+# Scale out to deploy over 500 and up to 1000 application instances using Azure Spring Apps Enterprise
+
+This article applies to ❌ Basic/Standard ✔️ Enterprise
+
+This article guides you on deploying up to 1000 application instances in Azure Spring Apps Enterprise. The feature supporting deployment of more than 500 instances is currently in Preview. This article outlines the limitations during the Preview stage. The Enterprise plan, crafted for handling substantial production workloads, supports a maximum of 1000 application instances per service. However, we recommend using a maximum of 500 instances in your production environment.
+
+## Definition
+
+The Azure Spring Apps Enterprise plan supports up to 1000 application instances per service instance. The number of application instances is the sum of all the application instances in the service instance. For example, if you have 100 applications in the service instance and each application has 10 replicas, then the total number of application instances is 1000.
+
+## Configure proper subnet ranges
+
+When you deploy Azure Spring Apps in an Azure virtual network, you need to configure the proper subnet ranges for your apps and services. The subnet ranges determine how many IP addresses are available for your apps and services to use. If the subnet ranges are too small, you might run out of IP addresses and encounter errors or failures.
+
+To avoid this problem, you should reserve subnet ranges that are large enough to support the number of application instances. For subnets, Azure reserves five IP addresses, and Azure Spring Apps requires at least three IP addresses. We recommend that you reserve at least the `/24` subnet ranges for the apps subnet.
+
+For more information about how to deploy an Azure Spring Apps instance in your virtual network, see [Deploy Azure Spring Apps in a virtual network](how-to-deploy-in-azure-virtual-network.md).
+
+## Restrictions
+
+Support for 1000 app instances is currently in the preview stage. The following sections describe the restrictions that you should understand when you try this feature.
+
+### VMware Tanzu® Build Service™
+
+VMware Tanzu Build Service automates container creation, management, and governance at enterprise scale. Tanzu Build Service uses the buildpacks project to turn application source code into container images.
+
+The builder is a Tanzu Build Service resource, which contains a set of buildpacks and a stack used in the process of building source code. The build number using the same builder should be less than 200. Otherwise, it's hard to reconcile all builds when the builder updates.
+
+The builds are generated when you deploy apps. We recommend that you create multiple customized builders to deploy apps when you have more than 200 apps or deployments.
+
+### Application Configuration Service for Tanzu
+
+Application Configuration Service for Tanzu is a central place to manage external properties for applications across all environments. This service is offered in two versions: Gen1 and Gen2. The Gen1 version mainly serves existing customers for backward compatibility purpose. Gen2 uses flux as the back end to communicate with Git repositories. Gen2 provides better performance compared to Gen1.
+
+The following table shows the benchmark for refresh times under different numbers of patterns. Be sure to carefully control the configuration pattern number based on these values to avoid unacceptable refresh performance.
+
+| Application Configuration Service generation | Duration to refresh under 100 patterns | Duration to refresh under 250 patterns | Duration to refresh under 500 patterns |
+|----------------------------------------------|----------------------------------------|----------------------------------------|----------------------------------------|
+| Gen1                                         | 330s                                   | 840s                                   | 1500s                                  |
+| Gen2                                         | 13s                                    | 100s                                   | 378s                                   |
+
+### Spring Cloud Gateway for VMware Tanzu
+
+Spring Cloud Gateway for VMware Tanzu handles the cross-cutting concerns for API development teams, such as single sign-on (SSO), access control, rate-limiting, resiliency, security, and more. You can accelerate API delivery using modern cloud native patterns using your choice of programming language for API development. Spring Cloud Gateway is a critical component for a microservices architecture.
+
+The performance of the gateway is closely related to the number of routes. In general, we recommend that you don't exceed 500 routes. When the gateway can't handle some requests with reasonably low latency or without errors, it can stress a gateway instance's performance.
+
+Spring Cloud Gateway is able to handle a high volume of traffic. To support the traffic, you should consider increasing the memory requested for API gateway instances so that each pod can handle more requests per second. To configure autoscale rules for the gateway to perform best when demand changes, see the [Set up autoscale settings for VMware Spring Cloud Gateway](how-to-configure-enterprise-spring-cloud-gateway.md#set-up-autoscale-settings-for-vmware-spring-cloud-gateway-in-azure-cli) section in [Configure VMware Spring Cloud Gateway](how-to-configure-enterprise-spring-cloud-gateway.md).
+
+Spring Cloud Gateway supports rolling restarts to ensure zero downtime and disruption. However, the current version of the gateway has a limitation that when it's rolling restarted, it may take longer to synchronize a large number of routes. This situation can cause incomplete route updates during the process. We're actively working on fixing this limitation and will provide an update through our documentation.
+
+## Next steps
+
+- [Build and deploy apps to Azure Spring Apps](quickstart-deploy-apps.md)
+- [Scale an application in Azure Spring Apps](how-to-scale-manual.md)
diff --git a/articles/spring-apps/quotas.md b/articles/spring-apps/quotas.md
@@ -29,7 +29,7 @@ The following table defines limits for the pricing plans in Azure Spring Apps.
 | vCPU                                | per app instance                       | 1                  | 4                                               | 8                                               | 4                                               | based on workload profile (for example, 16 in D16)    |
 | Memory                              | per app instance                       | 2 GB               | 8 GB                                            | 32 GB                                           | 8 GB                                            | based on workload profile (for example, 128GB in E16) |
 | Azure Spring Apps service instances | per region per subscription            | 10                 | 10                                              | 10                                              | 10                                              | 10                                                    |
-| Total app instances                 | per Azure Spring Apps service instance | 25                 | 500                                             | 500                                             | 400                                             | 1000                                                  |
+| Total app instances                 | per Azure Spring Apps service instance | 25                 | 500                                             | 1000                                            | 400                                             | 1000                                                  |
 | Custom Domains                      | per Azure Spring Apps service instance | 0                  | 500                                             | 500                                             | 500                                             | 500                                                   |
 | Persistent volumes                  | per Azure Spring Apps service instance | 1 GB/app x 10 apps | 50 GB/app x 10 apps                             | 50 GB/app x 10 apps                             | Not applicable                                  | Not applicable                                        |
 | Inbound Public Endpoints            | per Azure Spring Apps service instance | 10 <sup>1</sup>    | 10 <sup>1</sup>                                 | 10 <sup>1</sup>                                 | 10 <sup>1</sup>                                 | 10 <sup>1</sup>                                       |
diff --git a/articles/spring-apps/toc.yml b/articles/spring-apps/toc.yml
@@ -199,6 +199,8 @@ items:
       href: how-to-enterprise-deploy-static-file.md
     - name: Deploy large CPU and memory applications for Enterprise plan
       href: how-to-enterprise-large-cpu-memory-applications.md
+    - name: Deploy applications at scale for Enterprise plan
+      href: how-to-enterprise-deploy-app-at-scale.md
   - name: Manage
     items:
     - name: Start or stop a service
