1. Home
  2. Release Management Tools
  3. Spinnaker Reviews

Spinnaker Reviews

4 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 7.2 out of 100

Do you work for this company? Manage this listing

Show Filters 

Overall Rating

Reviewer's Company Size

Last Updated

By Topic

Industry

Department

Experience

Job Type

Role

Show All Filters

Reviews (1-2 of 2)

Debajit Kataki | TrustRadius Reviewer
May 21, 2018

Spinnaker for AWS Continuous Delivery and AMI restacking!

Debajit Kataki
Score 9 out of 10
Vetted Review
Verified User
Review Source
We use Spinnaker for continuous delivery in AWS and AWS AMI re-staking!
  • Spinnaker is very strong in its ability to baking of AMI(with ROSCO) and code deployments for Linux based ec2/AMI. Below are some more points:
  • Out of the box deployment strategies.
  • Open Source and active development.
  • Multi cloud deployments ( also can integrate with kubernetes)
  • Automated triggers.
  • Manual Judgements.
  • In-house bakery service, which helps in immutable deployments.
  • Easy pipeline setups using the UI , no need to write complex CFNs for code deployments.
  • "One click resize" of the underlying ec2s.
  • Exactly "one click rollback".
  • Pipelines can be scripted (SPEL)
  • Excellent search feature to search LBs , clusters etc from the UI.
  • Both high level and low level view of clusters, which has fine-grained options to control cloud infra from Spinnaker UI itself.
  • SSO and RBAC supported.
  • Wide range of deployment strategies like Blue-Green , Highlanders etc.
  • It does NOT support CFN based deployments
  • Windows based systems finds it difficult to onboard to Spinnaker.
  • Pipeline level access authorisation is not there.
  • Support for EBS volume encryption is probably missing.
  • Attach/detach EBS volumes during deployments is difficult.
  • No support to deploy the artifacts without re-creating the servers. Only pure immutable deployment are allowed.
  • Open-source - so good and bad!
  • Spinnaker on its own has 10 underlying micro services. Managing Spinnaker needs a focussed platform approach.
  • User authentication is easy but authorisation management is not straight forward.
We find Spinnaker a very useful tool, primarily due to the below reasons:

  1. Out of the box deployment strategies.
  2. Open Source and active development.
  3. Multi-cloud deployments ( also can integrate with k8s )
  4. Automated triggers.
  5. Manual Judgements.
  6. In-house bakery service, which helps in immutable deployments.
  7. Easy pipeline setups using the UI, no need to write complex CFNs for code deployments.
  8. "One click resize" of the underlying ec2s.
  9. Exactly "one-click rollback".
  10. Pipelines can be scripted. (SPEL)
  11. Excellent search feature to search LBs, clusters etc from the UI.
  12. Both high level and low-level view of clusters, which has fine-grained options to control cloud infra from Spinnaker UI itself.
  13. SSO and RBAC supported.
  14. Wide range of deployment strategies like Blue-Green, Highlanders etc.
Read Debajit Kataki's full review
Anonymous | TrustRadius Reviewer
May 18, 2018

Spinnaker is a great tool for CD in AWS

Verified User
Score 10 out of 10
Vetted Review
Verified User
Review Source
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.
  • 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.
  • 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
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.
Read this authenticated review

Spinnaker Scorecard Summary

Likelihood to Recommend (4)
7.2

About Spinnaker

Spinnaker is an open source continuous delivery platform with a range of cluster management and deployment management features, originally developed at Netflix.
Categories:  Release Management

Spinnaker Technical Details

Operating Systems: Unspecified
Mobile Application:No