Our main use case for Akuity Platform is automation based on test results. When we came up with this approach, we started using Akuity Platform, where our Argo CD helps us automate based on the test results in each environment. For example, if I want to publish a build and it passes the test cases, it goes to the next stage. We don't have this kind of check otherwise. As we have many clusters, they are tough to manage, so we started taking help from Akuity Platform.
Here is a specific example of how we use Akuity Platform in our workflow. Every time we need to deploy the services, the developers first push their code, and the code is deployed. Once it is deployed and all the test cases pass, we release the build to QA2 and QA3. The QA2 publish and QA3 publish are manual, and we need to publish each service one by one. To overcome this situation, we have our developer regression test. On top of that, we have all the test case results, and based on them, we get the result. Argo CD runs some test cases.
Once it passes, the build goes to the higher environment. After that, it goes to QA3. If everything passes and the test results are as expected, the build automatically goes to the next environment. Otherwise, it publishes the older version as required. If everything is successful, we don't need to manually go and publish all the time. We can release it in one click.
Beyond our main use case, in general, Akuity Platform helps us manage Argo CD, including scaling, managing, and security. If we deploy hundreds of applications at a time, it can sometimes crash. Akuity Platform also helps us with automation, similar to Argo CD.
