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 QA3 and QA2. The QA3 publish and QA2 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.
From a DevOps perspective, Akuity Platform has significantly improved our deployment and release management process.
One of the key benefits is that instead of promoting individual services separately, we can promote an entire project consisting of multiple microservices across different environments.
The promotion process is based on predefined success criteria and verification results. After deploying to an environment, the platform waits for the pods to become healthy and the required checks to pass before allowing the promotion to proceed to the next environment.
This helps us automate deployments, reduce manual intervention, ensure deployment stability, and maintain consistency across environments.
One of the best features of the Akuity Platform is its release promotion and artifact management capabilities. It allows us to promote releases from one environment to another based on predefined conditions and verification results.
Another useful feature is its integration with container registries such as Amazon ECR. Whenever a new Docker image version is published, Kargo can discover and track that version as a new Freight.
The Freight feature is particularly helpful because it maintains a history of available releases. We can view the previously published versions, select a specific version, and promote it whenever required. This also makes it easier to roll back to a previously stable release.
Akuity Platform also provides better management of Argo CD at scale. Instead of handling all the operational aspects of a self-managed Argo CD setup, we can use Akuity's managed platform to reduce control-plane maintenance and operational overhead.
Overall, features such as Freight management, environment-based promotions, verification, release history, and centralized Argo CD management help us improve deployment consistency, simplify release management, and reduce manual effort.
We have not been using Akuity Platform for a long period. Initially, we started with Argo CD, and we have been using these services for six months.
My thinking on Akuity Platform is clear: it is a good platform. We got to know that it is a test panel.