diff --git a/content/roadmaps/102-devops/content/105-infrastructure-as-code/100-service-mesh/readme.md b/content/roadmaps/102-devops/content/105-infrastructure-as-code/100-service-mesh/readme.md
index c0c119a25..4abfd06be 100644
--- a/content/roadmaps/102-devops/content/105-infrastructure-as-code/100-service-mesh/readme.md
+++ b/content/roadmaps/102-devops/content/105-infrastructure-as-code/100-service-mesh/readme.md
@@ -1 +1,6 @@
-# Service mesh
\ No newline at end of file
+# Service Mesh
+
+A service mesh, like the open source project Istio, is a way to control how different parts of an application share data with one another. Unlike other systems for managing this communication, a service mesh is a dedicated infrastructure layer built right into an app. This visible infrastructure layer can document how well (or not) different parts of an app interact, so it becomes easier to optimize communication and avoid downtime as an app grows.
+
+<ResourceGroupTitle>Free Content</ResourceGroupTitle>
+<BadgeLink colorScheme='yellow' badgeText='Read' href='https://www.redhat.com/en/topics/microservices/what-is-a-service-mesh'>What's a service mesh?</BadgeLink>