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-eureka-integration.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,19 +6,19 @@ author: craigshoemaker
6
6
ms.service: azure-container-apps
7
7
ms.custom: devx-track-extended-java
8
8
ms.topic: conceptual
9
-
ms.date: 07/15/2024
9
+
ms.date: 11/19/2024
10
10
ms.author: cshoe
11
11
---
12
12
13
13
# Tutorial: Integrate Admin for Spring with Eureka Server for Spring in Azure Container Apps
14
14
15
-
This tutorial will guide you through the process of integrating a managed Admin for Spring with a Eureka Server for Spring within Azure Container Apps.
15
+
This tutorial guides you through the process of integrating a managed Admin for Spring with a Eureka Server for Spring within Azure Container Apps.
16
16
17
17
This article contains some content similar to the "Connect to a managed Admin for Spring in Azure Container Apps" tutorial, but with Eureka Server for Spring, you can bind Admin for Spring to Eureka Server for Spring, so that it can get application information through Eureka, instead of having to bind individual applications to Admin for Spring.
18
18
19
-
By following this guide, you'll set up a Eureka Server for service discovery and then create an Admin for Spring to manage and monitor your Spring applications registered with the Eureka Server. This setup ensures that other applications only need to bind to the Eureka Server, simplifying the management of your microservices.
19
+
By following this guide, you set up a Eureka Server for service discovery and then create an Admin for Spring to manage and monitor your Spring applications registered with the Eureka Server. This setup ensures that other applications only need to bind to the Eureka Server, simplifying the management of your microservices.
20
20
21
-
In this tutorial, you will learn to:
21
+
In this tutorial, you learn to:
22
22
23
23
1. Create a Eureka Server for Spring.
24
24
2. Create an Admin for Spring and link it to the Eureka Server.
@@ -59,7 +59,7 @@ Before you begin, create the necessary resources by executing the following comm
59
59
|`ENVIRONMENT`| The Azure Container Apps environment name for your demo application. |
60
60
|`EUREKA_COMPONENT_NAME`| The name of the Eureka Server Java component. |
61
61
|`ADMIN_COMPONENT_NAME`| The name of the Admin for Spring Java component. |
62
-
|`CLIENT_APP_NAME`| The name of the container app that will bind to the Eureka Server. |
62
+
|`CLIENT_APP_NAME`| The name of the container app that binds to the Eureka Server.|
63
63
|`CLIENT_IMAGE`| The container image used in your Eureka Server container app. |
With the Eureka Server set up, you can now bind other applications to it for service discovery. And you can also monitor and manage these applications in the dashboard of Admin for Spring. Follow the steps below to create and bind a container app to the Eureka Server:
116
+
With the Eureka Server set up, you can now bind other applications to it for service discovery. And you can also monitor and manage these applications in the dashboard of Admin for Spring. Use the following steps to create and bind a container app to the Eureka Server:
117
117
118
118
Create the container app and bind it to the Eureka Server.
119
119
@@ -152,11 +152,11 @@ az containerapp create \
152
152
}'
153
153
```
154
154
155
-
Make sure to replace placeholder in between the `<>`brackets in the `AssignableScopes` value with your subscription ID.
155
+
Make sure to replace the `<SUBSCRIPTION_ID>`placeholder in the `AssignableScopes` value with your subscription ID.
156
156
157
157
1. Assign the custom role to your account on managed environment resource.
158
158
159
-
Get the resource id of the managed environment.
159
+
Get the resource ID of the managed environment.
160
160
161
161
```azurecli
162
162
export ENVIRONMENT_ID=$(az containerapp env show \
@@ -167,7 +167,7 @@ az containerapp create \
167
167
168
168
1. Assign the role to your account.
169
169
170
-
Before running this command, replace the placeholder in between the `<>`brackets with your user or service principal ID.
170
+
Before running this command, replace the `<USER_OR_SERVICE_PRINCIPAL_ID>`placeholder with your user or service principal ID.
171
171
172
172
```azurecli
173
173
az role assignment create \
@@ -200,9 +200,9 @@ az containerapp create \
200
200
201
201
This command returns the URL you can use to access the Eureka Server for Spring dashboard. Through the dashboard, your container app is also to you as shown in the following screenshot.
202
202
203
-
:::image type="content" source="media/java-components/spring-boot-admin.png" alt-text="Screenshot of the Admin for Spring dashboard." lightbox="media/java-components/spring-boot-admin.png":::
203
+
:::image type="content" source="media/java-components/spring-boot-admin.png" alt-text="Screenshot of the Admin for Spring dashboard." lightbox="media/java-components/spring-boot-admin.png":::
204
204
205
-
:::image type="content" source="media/java-components/eureka.png" alt-text="Screenshot of the Eureka Server for Spring dashboard." lightbox="media/java-components/eureka.png":::
205
+
:::image type="content" source="media/java-components/eureka.png" alt-text="Screenshot of the Eureka Server for Spring dashboard." lightbox="media/java-components/eureka.png":::
| Container app environment | Select **Create new** to create a new environment. |
112
112
113
113
1. On the **Create Container Apps environment** window, enter the following values:
114
114
@@ -182,7 +182,7 @@ Now that you have an existing environment and admin client container app, you ca
182
182
183
183
1. On the service menu, under **Services**, select **Services**.
184
184
185
-
1. Select the **+ Configure** dropdown, and select **Java component**.
185
+
1. Select the **Configure** dropdown, then select **Java component**.
186
186
187
187
1. On the **Configure Java component** pane, enter the following values:
188
188
@@ -224,7 +224,7 @@ Now that you have an existing environment and admin client container app, you ca
224
224
225
225
1. From the list, select **admin**.
226
226
227
-
1. Under **Bindings**, select the **App name** dropdown, and select **sample-admin-client**.
227
+
1. Under **Bindings**, select the **App name** dropdown, then select **sample-admin-client**.
228
228
229
229
1. Select the **Review** tab.
230
230
@@ -265,7 +265,7 @@ az containerapp update \
265
265
266
266
1. From the list, select **admin**.
267
267
268
-
1. Under **Bindings**, find the line for **sample-admin-client**, select it, and select **Delete**.
268
+
1. Under **Bindings**, find the line for **sample-admin-client**, select it, and then select **Delete**.
269
269
270
270
1. Select **Next**.
271
271
@@ -309,7 +309,7 @@ az containerapp update \
309
309
310
310
1. Assign the role to your account.
311
311
312
-
Before you run this command, replace the placeholder in between the `<>` brackets with your user or service principal ID.
312
+
Before you run this command, replace the placeholder - as indicated by the `<>` brackets - with your user or service principal ID or role name.
313
313
314
314
```azurecli
315
315
az role assignment create \
@@ -319,7 +319,7 @@ az containerapp update \
319
319
```
320
320
321
321
> [!NOTE]
322
-
> The <USER_OR_SERVICE_PRINCIPAL_ID> property usually should be the identity that you use to access the Azure portal. The <ROLE_NAME> property is the name that you assigned in step 1.
322
+
> The `<USER_OR_SERVICE_PRINCIPAL_ID>` value should be the identity that you use to access the Azure portal. The `<ROLE_NAME>` value is the name that you assigned in step 1.
323
323
324
324
1. Get the URL of the Admin for Spring dashboard.
325
325
@@ -328,7 +328,8 @@ az containerapp update \
328
328
--environment $ENVIRONMENT \
329
329
--resource-group $RESOURCE_GROUP \
330
330
--name $JAVA_COMPONENT_NAME \
331
-
--query properties.ingress.fqdn -o tsv
331
+
--query properties.ingress.fqdn \
332
+
--output tsv
332
333
```
333
334
334
335
This command returns the URL that you can use to access the Admin for Spring dashboard. With the dashboard, you can also see your container app, as shown in the following screenshot.
@@ -380,7 +381,7 @@ The following list details the admin component properties you can configure for
380
381
|`spring.boot.admin.monitor.timeout.*`| Key-value pairs with the timeout per `endpointId`. | Defaults to `default-timeout` value. |
381
382
|`spring.boot.admin.monitor.default-retries`| Default number of retries for failed requests. Requests that modify data (`PUT`, `POST`, `PATCH`, `DELETE`) are never retried. Individual values for specific endpoints can be overridden using `spring.boot.admin.monitor.retries.*`. |`0`|
382
383
|`spring.boot.admin.monitor.retries.*`| Key-value pairs with the number of retries per `endpointId`. Requests that modify data (`PUT`, `POST`, `PATCH`, `DELETE`) are never retried. | Defaults to `default-retries` value. |
383
-
|`spring.boot.admin.metadata-keys-to-sanitize`| Metadata values for the keys matching these regex patterns used to sanitize in all JSON output. Starting from Spring Boot 3, all actuator values are masked by default. For more information about how to configure the unsanitization process, see [Sanitize Sensitive Values](https://docs.spring.io/spring-boot/reference/actuator/endpoints.html#actuator.endpoints.sanitization). |`".*password$", ".*secret$", ".*key$", ".*token$", ".*credentials.*", ".*vcap_services$"`|
384
+
|`spring.boot.admin.metadata-keys-to-sanitize`| Metadata values for the keys matching these regex patterns used to sanitize in all JSON output. Starting from Spring Boot 3, all actuator values are masked by default. For more information about how to configure the unsanitization process, see [Sanitize Sensitive Values](https://docs.spring.io/spring-boot/reference/actuator/endpoints.html#actuator.endpoints.sanitization). |`".*password$", ".*secret$", ".*key$", ".*token$", ".*credentials.*", ".*vcap_services$"`|
384
385
|`spring.boot.admin.probed-endpoints`| For Spring Boot 1.x client applications, Spring Boot Admin probes for the specified endpoints using an `OPTIONS` request. If the path differs from the ID, you can specify this value as `id:path` - for example, `health:ping`. |`"health", "env", "metrics", "httptrace:trace", "threaddump:dump", "jolokia", "info", "logfile", "refresh", "flyway", "liquibase", "heapdump", "loggers", "auditevents"`|
385
386
|`spring.boot.admin.instance-proxy.ignored-headers`| Headers not to forwarded when making requests to clients. |`"Cookie", "Set-Cookie", "Authorization"`|
386
387
|`spring.boot.admin.ui.title`| The displayed page title. |`"Spring Boot Admin"`|
0 commit comments