Armory Reviews

The CDaaS product does a great job managing deployments of my k8s apps, and keeps me from having to code a bunch of logic in my build pipelines to deploy and verify my apps. While our K8s environment is not overly complex, we have had issue with deployments going awry in the past, and the capabilities of CDaaS has virtually eliminated those on the projects we've migrate to it.

Specific to CDaaS, it's more about the roadmap - it's a developing product, and doesn't yet support things outside of K8s. However, the approach to using webhooks and actions is a solid workaround for that issue while the product continues to get better and evolves to directly support the external technologies.

Reliability of deployments - this is enable us to be able to deploy more complex environments reliably.

ease of usage, user-friendly UI and documentation

We are yet exploring this product and currently no as such disliked any features.

using it to implement product pipelines and to run automation

Kubernetes is extremely complicated and figuring out (much less implementing) best practices for deploying it is a major challenge to do on your own. Using Armory gives you best-in-industry Kubernetes deployment tools and practices, without requiring you to do any complex set up or maintenance on your own. It works, it works well, and it gets out of your way (like any good tool). Armory lets you spend your time thinking about how to create great applications instead of wasting it figuring out how to deploy your applications.

It's a good tool (assuming you indeed have the problem it's design to solve, i.e. managing complex cloud deployments.) No complaints from us!

We need to deploy our application to Kubernetes in multiple regions and environments. Armory makes that simple.

Armory makes Continuous Delivery straightforward, with an amazingly concise starting point that took minimal time to get started with. As my team was ready to extend our deployments into more functionally detailed patterns, we were able to do so with help from solid documentation and responsive support. Armory's cadence for feature development and product support is consistent, and they listen well to their clients. With their help, we were able to round out our CD tooling quickly and keep our emphasis on development.

Armory is consistently progressing on this front, but granular visibility into the deployment objects and mechanisms is slightly less than what can be had by self-hosting. It's a trade-off between controlling your tools and being responsible for their maintenance/development. That said, Armory is VERY attentive to the needs of their clients and was excellent at receiving feedback, making avenues for submitting ideas readily available.

Armory provides a first-class solution for continuous delivery that met our needs without bringing a lot of extra overhead and duplicate tooling to the table. With Armory CDaaS, we were able to increase our release cadence and confidence in our pipleline at the same time, without needing to overhaul existing CI. Not to be cliche with the statement, but "it just worked." We were able to hand off to Armory on the far side of CI with a few extra lines of added yaml.

Integrations!! For ex: Helm chart and Kustomize along with alert/notification integration for tools such as slack. GithubStatus notification is one of my favourite! Also, webhook to trigger pipeline and SSO integration with service such as OKTA. Also, applications with multi-pipelines and mutli-stages is something amazing and new which I have seen and used with Armory Spinnkaer.

Pipeline as a code with Dinghyfile! I have not been able to setup and make Dinghyfile work with application that has multi-pipelines and multi-stages. Would love a better support for that.

Should try out armory once. This can solve the issues faced with other similar tools

I have been able to solve the deployment and upgrades issues with Spinnkaer. Canary, Blue/Green deployments are very smooth with Spinnkaer along with all the beautiful intergations.

The best part is integration with multiple tools and also detailed progress of each stage in pipeline view.

If something goes wrong, we can easily see the detailed view of what went wrong.

The only thing I don't like is sometimes some sub-stage like deployment promote fails but, overall pipeline status is Succeeded, which creates confusion sometimes, and we have to drill down further to see the status of each sub-stage.

It is a complete solution for deployment to Multiple clusters.

Little training is required but before using the tool.

the biggest problem we are solving is deployment of microservices to Kubernetes cluster.

One of the major benefit we are getting is after the pipeline is developed by the devops teams other teams like QA and perf are easily able to do the deployments to their environments.

Also the integration with github,Jenkins,Jfrog etc is very seamless.

Integration of Spinnaker with multiple components like Github, Jenkins, Canary deployment, and stack Rox. Easy to use pipeline and segregate different pipeline based on various projects.

Refresh rate is not good , need to manually refresh intermittently.

Really excellent product go for it for deployment related activity to k8

Deployment to K8 clusters. Easy to manage, automate and few inputs required at UI level

Spinnaker CI/CD pipeline design is easy and seemless. Spinnaker UI is user friendly and pipeline is displayed with substeps and complete pipeline execution details can be dug down for any pipeline execution failures.

There are no any downsides that we have come across so far.

Best to consider if your product needs to be deployed in cloud or containerised environment and end to end deployment process to be simple, easy and seemless.

Our cloud product hosting CI/CD backbone is spinnaker. It has made CI/CD pipeline easy and seemless.

Fast rollbacks and redeployments allowed us to fix mistakes quick

I believe the UI could be improved. It's not so bad but some things are not so easy to find if you don't now where to look for

We do deployment e redeployment of machine learning models. As I said to fix bad deployments.

It permits carrying out lines of code in the cloud with extraordinary adaptability. Can handle and ultimately send the whole foundation.

Supports majorly all cloud providers.

Its open source and is a growing community.

All in all smoothest when working with Jenkins.

Setup can be a headache.

It should work on pipeline as a code cause you need to recreate pipelines from scratch. Also, building plugins can reduce the headache.

Continuous delivery flow within the pipeline and providing a good UI to view and manage CI and deployment stage.

Integration for working on Kubernetes manifests.

Seeing all environment, all the stages on a single page. Helps in managaing it.