diff --git a/website/content/docs/k8s/service-sync.mdx b/website/content/docs/k8s/service-sync.mdx
index f1caeed303..182de64c47 100644
--- a/website/content/docs/k8s/service-sync.mdx
+++ b/website/content/docs/k8s/service-sync.mdx
@@ -16,6 +16,8 @@ as first-class Kubernetes services. This functionality is provided by the
 automatically installed and configured using the
 [Consul Helm chart](/docs/k8s/installation/install).
 
+![screenshot of a Kubernetes service in the UI](/img/k8s-service.png)
+
 **Why sync Kubernetes services to Consul?** Kubernetes services synced to the
 Consul catalog enable Kubernetes services to be accessed by any node that
 is part of the Consul cluster, including other distinct Kubernetes clusters.
diff --git a/website/public/img/k8s-service.png b/website/public/img/k8s-service.png
new file mode 100644
index 0000000000..24d1085e0a
Binary files /dev/null and b/website/public/img/k8s-service.png differ