Dataplanes diagram

website/content/docs/connect/dataplane/index.mdx

@@ -19,6 +19,8 @@ In standard deployments, Consul uses a control plane that contains both *server
 
 Consul Dataplane manages Envoy proxies and leaves responsibility for other functions to the orchestrator. As a result, it removes the need to run client agents on every pod. In addition, services no longer need to be reregistered to a local client agent after restarting a service instance, as a client agent’s lack of access to persistent data storage in Kubernetes deployments is no longer an issue.
 
+![Diagram of Consul Dataplanes in Kubernetes deployment](/img/dataplanes-diagram.png)
+
 ## Benefits
 
 **Fewer networking requirements**: Without client agents, Consul does not require bidirectional network connectivity across multiple protocols to enable gossip communication. Instead, it requires a single gRPC connection to the Consul servers, which significantly simplifies requirements for the operator.