From 913213af1e3ca44b3b4ad25e5de771c3e7b383d3 Mon Sep 17 00:00:00 2001
From: Hao Liu <44379968+TheRealHaoLiu@users.noreply.github.com>
Date: Tue, 13 Feb 2024 13:36:54 -0500
Subject: [PATCH] Update mesh-ingress.md

---
 docs/user-guide/advanced-configuration/mesh-ingress.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/docs/user-guide/advanced-configuration/mesh-ingress.md b/docs/user-guide/advanced-configuration/mesh-ingress.md
index 754b67eae..824185bdf 100644
--- a/docs/user-guide/advanced-configuration/mesh-ingress.md
+++ b/docs/user-guide/advanced-configuration/mesh-ingress.md
@@ -47,6 +47,11 @@ After AWXMeshIngress has been successfully created a new Instance with the same
 
 The Instance should have at least 2 Listener Address
 
+In this example, the mesh ingress has two listener addresses:
+
+- one for internal, that is used for peering to by all control nodes (top)
+- one for external, that is exposed to a route so external execution nodes can peer into it (bottom))
+
 ![mesh ingress instance listener address on awx ui](mesh-ingress-instance-listener-address-on-awx-ui.png)
 
 When selecting peer for new instance the mesh ingress instance should now be present as a option.