Overall Satisfaction with Spinnaker
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.
Do you think Spinnaker delivers good value for the price?
Yes
Are you happy with Spinnaker's feature set?
Yes
Did Spinnaker live up to sales and marketing promises?
Yes
Did implementation of Spinnaker go as expected?
No
Would you buy Spinnaker again?
Yes