Spinnaker - A powerful Continuous Deployment solution with all that you need out of the box.
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 …
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.
Recent Reviews
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?
8 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…
Product Details
- About
- Tech Details
What is Spinnaker?
Spinnaker Technical Details
| Operating Systems | Unspecified |
|---|---|
| Mobile Application | No |
Comparisons
Compare with
Reviews and Ratings
(5)Reviews
(1-3 of 3)Companies can't remove reviews or game the system. Here's why
May 31, 2021
Spinnaker - A powerful Continuous Deployment solution with all that you need out of the box.
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.
- 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.
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.
- 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!
May 18, 2018
Spinnaker is a great tool for CD in AWS
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
- 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