TrustRadius Insights for Spinnaker are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Easy-to-use User Interface: Users have praised the user interface of Spinnaker, describing it as good, perfect, sleek, and user-friendly. The UI was considered to be perfect and made it easy for users to navigate and use the tool effectively.
Seamless Deployment Process: Users appreciated the easy setup and configuration of Spinnaker, making it a go-to tool for deploying EC2 and Kubernetes. They found it very easy to use and coordinate build and deployment processes on multiple clouds.
Wide Integration with Cloud Providers: The fact that Spinnaker integrates well with many cloud providers such as GCP, AWS, and Kubernetes was highly appreciated by users. This seamless integration allows them to fully control and deploy their entire infrastructure without any hassle.
Leveraging Spinnaker to enable Fast, Frequent, Fearless deployments, delightful service operation, and increased AWS migrations. We are adopting Spinnaker because we believe in the patterns and practices it promotes around CICD and agile, iterative delivery. We believe as the team building this solution for the company we must be early adopters of these practices, we must evangelize those patterns and practices, and we must use them deliver value for customers as quickly as possible.
Pros
The immutable way of deployment is one of its greatest advantages.
We have a strict policy to restock our instances with new images very frequently and this can be done very seamlessly via Spinnaker
Rollback/ resize of clusters is one of the coolest features of Spinnaker.
Cons
Spinnaker on its own has 10 underlying micro services. Managing Spinnaker needs a focussed platform approach
No support to deploy the artifacts without re-creating the servers. Only pure immutable deployment are allowed.
No authorization at pipelines level
Likelihood to Recommend
Spinnaker suits well for applications which are stateless and can adapt to an immutable architecture of deployment. But for applications which are stateful and cannot afford to spin up new servers for every deployment doesn't go well with Spinnaker. It can handle only deployments which are VM based and cannot support deployments to serverless architecture like AWS Lambda etc.
VU
Verified User
Engineer in Engineering (Computer Software company, 501-1000 employees)