Skip to main content
TrustRadius
Spinnaker

Spinnaker

Overview

What is Spinnaker?

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

Read more
Recent Reviews

TrustRadius Insights

Users have found the software to be effective for continuous delivery and deployment. It allows them to automate the entire process and …
Continue reading
Read all reviews
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Spinnaker?

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

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

10 people also want pricing

Alternatives Pricing

What is Octopus Deploy?

Australian company Octopus Deploy offers their eponymous automated deployment and release management software that integrates with the user's preferred CI server and adds deployment & ops automation capabilities. Octopus Deploy enables developers, release managers, and operations folks to bring all…

What is Liquibase?

Liquibase is a database change management tool that helps teams release software faster and safer by bringing the database change process into existing CI/CD automation. According to the 2021 Accelerate State of DevOps Report, elite performers are 3.4 times more likely to incorporate database…

Return to navigation

Product Details

What is Spinnaker?

Spinnaker Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(5)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Users have found the software to be effective for continuous delivery and deployment. It allows them to automate the entire process and monitor deployments without needing to log into consoles. The software enables quick deployments to various environments including Sandbox, Test, Branch, QA, Systest, Sectest, Staging, and PROD. It has been instrumental in transitioning from manual release and deployment processes to a one-click deployment functionality, reducing bottlenecks and the need for constant supervision.

Users have successfully implemented continuous deployment on Kubernetes clusters using the software alongside Jenkins as a CI tool. The software has simplified deployments in client environments where complex processes were previously required, resulting in over 200 successful deployments in the past 6 months. Users have found it helpful for solving cloud hosting issues and seamlessly integrating software. They appreciate the ability to control and manage deployments in a multi-account setup through a single-point deployment tool. The software supports continuous deployment of Kubernetes manifests and delivery to AWS.

It facilitates the deployment of AMIs on AWS EC2 instances using a CDO model. Particularly useful for cloud-based deployments, especially on AWS, it provides a visual environment for managing CI and deployment steps. While some users have encountered limitations with non-JVM projects, others have found success using the software as their main CD platform for Kubernetes-based products. Users have plans to expand deployment to other cloud providers like Azure. The software is being used by specific teams and read-only profiles for the development team.

Users adopt the software to enable fast, frequent, and fearless deployments, improve service operations, and facilitate AWS migrations. It promotes patterns and practices around CI/CD and agile, iterative delivery, which users believe brings value to their customers.

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.

Dated User Interface: Several users have mentioned that they find the user interface of Spinnaker to be dated and sometimes struggle to locate certain features or functions.

Difficult Configuration Process: Many reviewers have expressed frustration with the setup and configuration process of Spinnaker, describing it as cumbersome and even a nightmare in some cases. Some users also noted that the knowledge base lacks important information for specific setups.

Lack of Plugin Options: A common complaint among users is the lack of plugin options similar to Jenkins, making it challenging to manage source control, run tests, and build packages. This limitation has caused difficulties for some reviewers in their workflow.

Users commonly recommend:

  1. Consider using GitLab instead of the current tool invested in. Many users believe that GitLab is a better alternative and can offer more benefits.

  2. Start utilizing Spinnaker for faster deployments and make customized changes to Spinnaker pods for specific use cases. Users find that Spinnaker enables them to streamline their deployment processes and tailor it to their specific needs.

  3. Take advantage of the available resources to understand the runtime behavior of Spinnaker. Users recommend joining the Slack community, reading the documentation, blogs, and watching videos from the Spinnaker summit to gain valuable insights into how Spinnaker operates.

Overall, users highly recommend trying out Spinnaker as it offers many advantages, such as numerous plugins and support for deploying cloud-based delivery models. However, they acknowledge that setting up and configuring everything in Spinnaker can be time-consuming and requires effort. Despite this initial investment, many users find that once installed and configured, Spinnaker significantly simplifies and enhances their work processes.

Reviews

(1-3 of 3)
Companies can't remove reviews or game the system. Here's why
Erlon Sousa Pinheiro | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We are using Spinnaker as our main CD platform for one of our products which is based on Kubernetes. At this moment, the environment is based in just one cloud provider (AWS) but we have plans to deploy also in Azure. Currently it is being used just for my team, with some read-only profiles for people from development team.
  • Fast deployments.
  • Can be integrated with a good variety of other products.
  • Also provides some insights from your environment.
  • Integration with external authentication mechanism is not that simple.
  • Its configuration is made by a external tool (halyard). Would be better if we could configure it by using its own frontend.
  • Its user interface is some times a bit confusing.
Spinnaker is a strong solution for Continuous Deployment being able to manage enormous environments in an easy way. Even Spinnaker being able to manage environments based on cloud instances (ec2 for example) I believe it is more suitable for containerized environments. Mainly in Kubernetes where it excels as a reliable and safe tool.
  • Continuous Deployment in Kubernetes Environments.
  • Access control for non technical users.
  • Integration with already used by our organization.
  • By using Spinnaker we are able to deploy new versions of our product quickly.
  • A deployment takes in average 2 minutes.
  • Our investment on Spinnaker was just time learning it.
Even Jenkins being originally a Continuous Integration solution, I've used it as a Continuous Deployment solution as well, but Spinnaker brought to me a more focused approach allowing us to spend less time by creating and managing pipelines. While on Jenkins we need to install dozens of plugin to achieve our goals, Spinnaker has all what we need out of the box. You just need to enable the feature through halyard and start to use it.
Debajit Kataki | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
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.
  • It's open source!
  • RPM based deployments can be scripted at Maven file itself , so very easy!
  • RPM based deployments bundles all code and configs together, so awesome!
We get a centralised view of all pipelines in single place. This helps for a large enterprise. Maven is very popular, so generating RPM from existing POM.xml is cool!
Score 10 out of 10
Vetted Review
Verified User
Incentivized
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.
  • As we are using it on a large scale, hosting and maintaining it is affordable.
  • For few of the BU where there are fewer applications in Cloud. Hosting it and maintaining is an overhead and not very cost effective.

• Pipeline Expressiveness

• Self-Service/Override

• Visibility of Client Teams

• Operability of Client Teams -

• High-Quality Integrations (AWS, IHP, Google)

• Extensibility – (Ability to add code)

• The maturity of Deployment Process

• Speed/Ease of Onboarding

Return to navigation