What components are common in a service mesh?

Tracing and log storage are typically functionalities that a service mesh integrates with or provides data for, but they are not the core architectural components of the service mesh itself.

Circuit breaking is a feature implemented by the service mesh's data plane, but Pod scheduling is a core function of Kubernetes, not a component of the service mesh.

While a service mesh operates at runtime, 'runtime plane' is not a standard architectural term for a service mesh; the correct terminology is data plane and control plane.

A service mesh is logically divided into a data plane, which consists of intelligent proxies (sidecars) deployed alongside service instances, and a control plane, which provides management, configuration, and policy enforcement for these proxies. The service proxies intercept and handle network traffic, while the control plane configures their behavior for features like traffic management, security, and observability.