Skip to content

Commit 630d2c0

Browse files
update TOC
1 parent 5af94b5 commit 630d2c0

File tree

2 files changed

+6
-3
lines changed

2 files changed

+6
-3
lines changed

articles/container-apps/TOC.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -384,6 +384,9 @@
384384
- name: Query managed component logs
385385
href: java-component-logs.md
386386
displayName: java
387+
- name: Create a highly-available Eureka server component cluster
388+
href: java-eureka-server-highly-available.md
389+
displayName: java
387390
- name: Billing & quotas
388391
items:
389392
- name: Billing

articles/container-apps/java-eureka-server-highly-available.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: "Tutorial: Create a highly available Eureka service in Azure Container Apps"
3-
description: Learn to create a highly available Eureka service in Azure Container Apps.
2+
title: "Tutorial: Create a highly-available Eureka server component cluster in Azure Container Apps"
3+
description: Learn to create a highly-available Eureka service in Azure Container Apps.
44
services: container-apps
55
author: craigshoemaker
66
ms.service: azure-container-apps
@@ -11,7 +11,7 @@ ms.author: cshoe
1111
#customer intent: As a developer, I want to create an Eureka server cluster so that I can ensure there is no downtime of my service registries regardless of load and failures.
1212
---
1313

14-
# Tutorial: Create a highly available Eureka service in Azure Container Apps
14+
# Tutorial: Create a highly-available Eureka server component cluster in Azure Container Apps
1515

1616
In this tutorial, you learn to create a Eureka service designed to remain operational in the face of failures and high demand. Building a highly available Eureka service ensures the service registry is always available to clients regardless of demand.
1717

0 commit comments

Comments
 (0)