A perfect service mesh should establish the ORASTAR rules without having to code anything at the microservice level:

• Observability: The control plane provides the observability of services running in the data plane.
• Routing: The routing rules for traffic management can be defined either graphically or through the use of configuration files and then pushed down from the control plane to all the data planes.
• Automatic scaling: The control plane services automatically scale to handle the increased workload.
• Separation of duties: The control plane UI allows operations to manage the service mesh independent of the development team.
• Trust: It pushes down secure communication protocols to the data planes and provides automatic renewal and management of certificates.
• Automatic service registration and discovery: The control plane integrates with the Kubernetes API server and discovers the service automatically as it's registered through application deployment procedures.
• Resilient: Pushes resiliency rules to all of the data planes. This acts as a sidecar proxy for traffic management.

Let's understand these rules in more detail.