Merge pull request #11995 from hashicorp/l7-routing-screenshots

Adding UI screenshots to L7 overview

package-lock.json

@@ -0,0 +1,3 @@
+{
+  "lockfileVersion": 1
+}

website/content/docs/connect/config-entries/service-resolver.mdx

@@ -23,6 +23,12 @@ and discovery terminates.
 - Service resolver config entries are a component of [L7 Traffic
   Management](/docs/connect/l7-traffic-management).
 
+## UI 
+
+Once a `service-resolver` is successfully entered, you can view it in the UI. Service routers, service splitters, and service resolvers can all be viewed by clicking on your service then switching to the *routing* tab.
+
+![screenshot of service resolver in the UI](/img/l7-routing/Resolver.png)
+
 ## Sample Config Entries
 
 ### Filter on service version

website/content/docs/connect/config-entries/service-router.mdx

@@ -36,6 +36,13 @@ service of the same name.
   to any configured
   [`service-resolver`](/docs/connect/config-entries/service-resolver).
 
+## UI 
+
+
+Once a `service-router` is successfully entered, you can view it in the UI. Service routers, service splitters, and service resolvers can all be viewed by clicking on your service then switching to the *routing* tab. 
+
+![screenshot of service router in the UI](/img/l7-routing/Router.png)
+
 ## Sample Config Entries
 
 ### Path prefix matching

website/content/docs/connect/config-entries/service-splitter.mdx

@@ -39,6 +39,12 @@ resolution stage.
   to any configured
   [`service-resolver`](/docs/connect/config-entries/service-resolver).
 
+## UI 
+
+Once a `service-splitter` is successfully entered, you can view it in the UI. Service routers, service splitters, and service resolvers can all be viewed by clicking on your service then switching to the *routing* tab.
+
+![screenshot of service splitter in the UI](/img/l7-routing/Splitter.png)
+
 ## Sample Config Entries
 
 ### Two subsets of same service

website/content/docs/connect/l7-traffic/index.mdx

@@ -33,7 +33,7 @@ Connect proxy upstreams are discovered using a series of stages: routing,
 splitting, and resolution. These stages represent different ways of managing L7
 traffic.
 
-![diagram showing l7 traffic discovery stages: routing to splitting to resolution](/img/l7-traffic-stages.svg)
+![screenshot of L7 traffic visualization in the UI](/img/l7-routing/full.png)
 
 Each stage of this discovery process can be dynamically reconfigured via various
 [configuration entries](/docs/agent/config-entries). When a configuration
@@ -44,6 +44,8 @@ entry is missing, that stage will fall back on reasonable default behavior.
 A [`service-router`](/docs/connect/config-entries/service-router) config
 entry kind is the first configurable stage.
 
+![screenshot of service router in the UI](/img/l7-routing/Router.png)
+
 A router config entry allows for a user to intercept traffic using L7 criteria
 such as path prefixes or http headers, and change behavior such as by sending
 traffic to a different service or service subset.
@@ -59,6 +61,8 @@ can be found in the `service-router` documentation.
 A [`service-splitter`](/docs/connect/config-entries/service-splitter) config
 entry kind is the next stage after routing.
 
+![screenshot of service splitter in the UI](/img/l7-routing/Splitter.png)
+
 A splitter config entry allows for a user to choose to split incoming requests
 across different subsets of a single service (like during staged canary
 rollouts), or perhaps across different services (like during a v2 rewrite or
@@ -84,6 +88,8 @@ can be found in the `service-splitter` documentation.
 A [`service-resolver`](/docs/connect/config-entries/service-resolver) config
 entry kind is the last stage.
 
+![screenshot of service resolver in the UI](/img/l7-routing/Resolver.png)
+
 A resolver config entry allows for a user to define which instances of a
 service should satisfy discovery requests for the provided name.
 
@@ -118,4 +124,4 @@ can be found in the `service-resolver` documentation.
 
 -> **Note:** `service-resolver` config entries kinds can function at L4 (unlike
 `service-router` and `service-splitter` kinds). These can be created for
-services of any protocol such as `tcp`.
+services of any protocol such as `tcp`.