Developers can deploy autoscaling policies alongside their application manifests into existing CI/CD pipelines and GitOps workflows. You can deploy Tanzu Service Mesh Service Autoscaler non-intrusively as part of the development process for testing and simulation purposes and for production.

A user commits autoscaler configurations using the Definition custom resource to a Git branch. After the code changes are reviewed and merged, ArgoCD (or another GitOps tool) applies the new configurations. Then the autoscaler responds to the changes.



Use Case 5 Example

For this example, we installed a private Git server called Gitea. We also installed ArgoCD as our GitOps tool. Users can choose from several other solutions for both functions.

This screenshot shows that Gitea is running locally on our cluster. Section A is the name of our project and repository. The text highlighted in the yellow rectangular box (B) shows our manifest files and the autoscaling definitions (ASDs) that we want to deploy in our cluster.

Argo CD keeps the Kubernetes configurations in sync with the configurations in the repository. When we commit a manifest file to the Git repo, it is deployed in our cluster. In this example, a manifest file can be an application or an ASD. Argo CD also shows whether a deployment was successful.