Istio Diagram Creation GuidelinesServiceServiceServiceUse a gray rectangle with rounded corners to represent a VM or pod place a label on the top left corner.Use a white rectangle with round corners to represent a service. Include the compute icon to represent specific workloads.Add the Envoy logo on a white rectangle with round corners to represent an Envoy proxy. Combine the visual cues as needed to represent the appropriate level of detail.Represent configuration objects as services with their own backends and Envoy proxies. Add the Istio logo to distinguish them.Use the following RGB values:Use the FontAwesome icons whenever possible.Use official logos only with permission and with the appropriate legal disclaimer.Example: Configurable traffic routing rules* All product names, logos, and brands are property of their respective owners. All company, product and service names used in this website are for identification purposes only. Use of these names, logos, and brands does not imply endorsement.Use lines to connect the components.Avoid crossing lines. Add arrows to determine direction. Place labels below the line to avoid typography issues.Use a blue-dashed rectangle without filling and with round corners to represent an Istio mesh. Use the Istio logo or “Istio Mesh” as a labelMy Backend: VM or podIstio MeshBidirectional monitoring trafficData plane trafficControl plane traffic or configurationRepresent Istio components as services in their own backend. Label them accordingly: Pilot, Galley, Mixer, or Citadel. Add the Istio logo and labels to distinguish them from other services.PilotMixerBlue-dashed lines denote control traffic or configurationsGreen-solid lines denote data plane traffic.Orange-dotted lines denote monitoring or telemetry traffic.External trafficGray lines denote traffic outside the mesh.To represent multiple workloads within a backend, just stack and label the representations.Service 1Service 2Virtual serviceGatewayService entryCertificateCertificateAuthorityContainerDiscoveryEncryptedCloudKurbernetes*Multiple services on a single backend.Service v1Service v2Multiple versions of a service.Configurable traffic routing rulesService entryEgressServiceService v1Service v2IngressVirtual serviceBlueR=51 G=102 B=153GreenR=0 G=153B=0PinkR=255G=0B=255GrayR=102G=102B=102OrangeR=255G=102B=0