add include

Author: craigshoemaker

articles/container-apps/java-admin-eureka-integration.md

@@ -6,7 +6,7 @@ author:
 ms.service: container-apps
 ms.custom: devx-track-extended-java
 ms.topic: conceptual
-ms.date: 07/03/2024
+ms.date: 07/08/2024
 ms.author: 
 ---
 
@@ -38,13 +38,7 @@ To complete this tutorial, you need the following items:
 
 When running managed Java components in Azure Container Apps, be aware of the following details:
 
-| Item | Explanation |
-|---|---|
-| **Scope** | The Java components run in the same environment as the connected container apps. |
-| **Scaling** | Both the Eureka Server and Admin for Spring have fixed scaling properties (`minReplicas` and `maxReplicas` set to `1`). |
-| **Resources** | The resource allocation for both components is fixed. Each is allocated 0.5 CPU cores and 1Gi of memory. |
-| **Pricing** | Billing falls under consumption-based pricing. Resources consumed by managed Java components are billed at active/idle rates. You can delete components that are no longer in use to stop billing. |
-| **Binding** | Container apps connect to managed Java components via a binding, which injects configurations into container app environment variables. |
+[!INCLUDE [container-apps/component-considerations.md](../../includes/container-apps/component-considerations.md)]
 
 ## Setup
 

articles/container-apps/java-admin.md

@@ -43,13 +43,7 @@ To complete this project, you need the following items:
 
 When running Admin for Spring in Azure Container Apps, be aware of the following details:
 
-| Item | Explanation |
-|---|---|
-| **Scope** | The Admin for Spring component runs in the same environment as the connected container app. |
-| **Scaling** | The Admin for Spring component can’t scale. The scaling properties `minReplicas` and `maxReplicas` are both set to `1`. |
-| **Resources** | The container resource allocation for Admin for Spring component is fixed. The number of the CPU cores is 0.5, and the memory size is 1Gi. |
-| **Pricing** | The Admin for Spring component billing falls under consumption-based pricing. Resources consumed by managed Java components are billed at the active/idle rates. You can delete components that are no longer in use to stop billing. |
-| **Binding** | Container apps connect to a Admin for Spring component via a binding. The bindings inject configurations into container app environment variables. Once a binding is established, the container app can read the configuration values from environment variables and connect to the Admin for Spring. |
+[!INCLUDE [container-apps/component-considerations.md](../../includes/container-apps/component-considerations.md)]
 
 ## Setup
 

includes/container-apps/component-considerations.md

@@ -0,0 +1,15 @@
+---
+author: craigshoemaker
+ms.service: container-apps
+ms.topic:  include
+ms.date: 05/08/2024
+ms.author: cshoe
+---
+
+| Item | Explanation |
+|---|---|
+| **Scope** | Components run in the same environment as the connected container app. |
+| **Scaling** | Component can’t scale. The scaling properties `minReplicas` and `maxReplicas` are both set to `1`. |
+| **Resources** | The container resource allocation for components is fixed. The number of the CPU cores is 0.5, and the memory size is 1Gi. |
+| **Pricing** | Component billing falls under consumption-based pricing. Resources consumed by managed components are billed at the active/idle rates. You can delete components that are no longer in use to stop billing. |
+| **Binding** | Container apps connect to a component via a binding. The bindings inject configurations into container app environment variables. Once a binding is established, the container app can read the configuration values from environment variables and connect to the component. |