Skip to content

Commit 9b189f0

Browse files
authored
Fix formatting of multi-cluster health check consistency (#852)
1 parent 200a087 commit 9b189f0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/concepts/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ In the context of Kubernetes, Amazon VPC Lattice helps to simplify the following
5353
After configuring your services with the AWS Gateway API Controller, you can facilitate advanced traffic management and application layer routing between services on those clusters without dealing with the underlying infrastructure.
5454
VPC Lattice handles a lot of the details for you without needing things like sidecars.
5555

56-
**Multi-cluster health check consistency**: When using TargetGroupPolicy with ServiceExport resources, health check configurations are automatically propagated across all clusters participating in the service mesh. This ensures consistent health monitoring behavior regardless of which cluster contains the route resource, eliminating configuration drift and improving reliability in multi-cluster deployments.
56+
- **Multi-cluster health check consistency**: When using TargetGroupPolicy with ServiceExport resources, health check configurations are automatically propagated across all clusters participating in the service mesh. This ensures consistent health monitoring behavior regardless of which cluster contains the route resource, eliminating configuration drift and improving reliability in multi-cluster deployments.
5757
- **Cross-platform access**: VPC Lattice allows access to serverless and Amazon EC2 features, as well as Kubernetes cluster features.
5858
This gives you a way to have a consistent interface to multiple types of platforms.
5959
- **Implement a defense-in-depth strategy**: Secure communication between services and networks.

0 commit comments

Comments
 (0)