Use Case 1: Use Service Autoscaling Based on SLI Thresholds to meet business needs and improve microservice behaviour

You can configure Tanzu Service Mesh Service Autoscaler to meet the needs of the business and improve the behavior of the microservices that are being targeted by the autoscaler.

You can set Tanzu Service Mesh Service Autoscaler ahead of time to determine when a scaling action should occur based on latencies, traffic, and saturation of server resources. When a scaling action takes place, you can configure the extent to which it responds, whether it be proportional or absolute, how quickly the scaling is implemented, and what should be done in case of insufficient metrics information. In this way, you can do scaling automatically in a predictive manner to ensure reliable operations.

If you are measuring the performance of a single service, you can configure using a Kubernetes custom resource definition (CRD). However, if the scaling impact should flow through all your cluster namespaces for the target service, you can configure using the GNS-scoped autoscaling policy through the Tanzu Service Mesh Console UI.