You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/container-apps/java-admin.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,15 +6,15 @@ author: craigshoemaker
6
6
ms.service: container-apps
7
7
ms.custom: devx-track-extended-java
8
8
ms.topic: conceptual
9
-
ms.date: 07/03/2024
9
+
ms.date: 07/08/2024
10
10
ms.author: cshoe
11
11
---
12
12
13
13
# Tutorial: Connect to a managed Admin for Spring in Azure Container Apps (preview)
14
14
15
15
The Admin for Spring managed component offers an administrative interface for Spring Boot web applications that expose actuator endpoints. As a managed component in Azure Container Apps, you can easily bind your container app to Admin for Spring for seamless integration and management.
16
16
17
-
This tutorial guides shows you how to create an Admin for Spring Java component and bind it to your container app so you can monitor and manage your Spring applications with ease.
17
+
This tutorial shows you how to create an Admin for Spring Java component and bind it to your container app so you can monitor and manage your Spring applications with ease.
18
18
19
19
:::image type="content" source="media/java-components/sba-overview.png" alt-text="Overview of the Admin for Spring insights dashboard." lightbox="media/java-components/sba-overview.png":::
20
20
@@ -46,9 +46,9 @@ When running Admin for Spring in Azure Container Apps, be aware of the following
46
46
| Item | Explanation |
47
47
|---|---|
48
48
|**Scope**| The Admin for Spring component runs in the same environment as the connected container app. |
49
-
|**Scaling**| The Admin for Spring can’t scale. The scaling properties `minReplicas` and `maxReplicas` are both set to `1`. |
50
-
|**Resources**| The container resource allocation for Admin for Spring is fixed. The number of the CPU cores is 0.5, and the memory size is 1Gi. |
51
-
|**Pricing**| The Admin for Spring 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. |
49
+
|**Scaling**| The Admin for Spring component can’t scale. The scaling properties `minReplicas` and `maxReplicas` are both set to `1`. |
50
+
|**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. |
51
+
|**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. |
52
52
|**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. |
53
53
54
54
## Setup
@@ -104,7 +104,7 @@ The following commands help you create your resource group and Container Apps en
104
104
105
105
## Use the component
106
106
107
-
Now that you have an existing environment, you can create your container app and bind it to a Java component instance of Admin for Spring.
107
+
Now that you have an existing environment, you can create your container app and bind it to a Java component instance of Admin for Spring component.
108
108
109
109
1. Create the Admin for Spring Java component.
110
110
@@ -138,7 +138,7 @@ Now that you have an existing environment, you can create your container app and
This property indicates that the Admin for Spring client should prefer the IP address of the container app instance when connecting to the Admin for Spring server.
141
+
This property indicates that the Admin for Spring component client should prefer the IP address of the container app instance when connecting to the Admin for Spring server.
142
142
143
143
You can also [remove a binding](admin-for-spring-usage.md#unbind) from your application.
144
144
@@ -161,7 +161,7 @@ Now that you have an existing environment, you can create your container app and
161
161
}'
162
162
```
163
163
164
-
Make sure to replace placeholder in between the `<>` brackets in the `AssignableScopes` value with your subscription ID.
164
+
Make sure to replace the placeholders in between the `<>` brackets with your values.
165
165
166
166
1. Assign the custom role to your account on managed environment resource.
0 commit comments