Spinnaker Reviews & Insights

Score7.9 out of 10

5 Reviews and Ratings

Community insights

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.

Reviews

3 Reviews

Spinnaker - A powerful Continuous Deployment solution with all that you need out of the box.

Rating: 7 out of 10

Incentivized

April 27, 2021

Use Cases and Deployment Scope

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.

Pros

Fast deployments.
Can be integrated with a good variety of other products.
Also provides some insights from your environment.

Cons

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.

Likelihood to Recommend

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.

Erlon Sousa Pinheiro

Senior Devops Engineer in Information Technology at SOTI (1001-5000 employees)

Vetted Review

2 years of experience

View profile

Spinnaker for AWS Continuous Delivery and AMI restacking!

Rating: 9 out of 10

Incentivized

May 21, 2018

Use Cases and Deployment Scope

We use Spinnaker for continuous delivery in AWS and AWS AMI re-staking!

Pros

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.

Cons

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.

Likelihood to Recommend

We find Spinnaker a very useful tool, primarily due to the below reasons:

Out of the box deployment strategies.
Open Source and active development.
Multi-cloud deployments ( also can integrate with k8s )
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.

Debajit Kataki

Sr. Devops Mgr. ( Tools, automations , Release Engineering/ CICD , AWS ) in Engineering at Intuit India (1001-5000 employees)

Vetted Review

2 years of experience

View profile

Spinnaker is a great tool for CD in AWS

Rating: 10 out of 10

Incentivized

May 18, 2018

Use Cases and Deployment Scope

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.

Verified User

Engineer in Engineering (501-1000 employees)

Vetted Review

1 year of experience

Loading Reviews List....

Spinnaker for AWS Continuous Delivery and AMI restacking!

Rating: 9 out of 10

Incentivized

May 21, 2018

Use Cases and Deployment Scope

We use Spinnaker for continuous delivery in AWS and AWS AMI re-staking!

Pros

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.

Cons

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.

Likelihood to Recommend

We find Spinnaker a very useful tool, primarily due to the below reasons:

Out of the box deployment strategies.
Open Source and active development.
Multi-cloud deployments ( also can integrate with k8s )
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.

Debajit Kataki

Sr. Devops Mgr. ( Tools, automations , Release Engineering/ CICD , AWS ) in Engineering at Intuit India (1001-5000 employees)

Vetted Review

2 years of experience

View profile