Spinnaker

Install, configure, and update your Spinnaker instance with halyard, Spinnaker's CLI tool

Require a manual approval prior to releasing an update with a manual judgement stage

Create deployment pipelines that run integration and system tests, spin up and down server groups, and monitor rollouts

Built-in deployment strategy for zero-downtime releases with easy rollback capability

Built-in deployment strategy for gradual rollout with monitoring and automatic rollback on failure

Configure pipelines with built-in deployment strategies such as highlander and blue/green, with rolling blue/green and canary in active development, or define custom strategies

Create and deploy immutable images for faster rollouts, easier rollbacks, and elimination of hard to debug configuration drift issues

Bake immutable VM images via Packer, which comes packaged with Spinnaker and offers support for Chef and Puppet templates

Listen to events, collect artifacts, and trigger pipelines from Jenkins or Travis CI

Tie your releases to monitoring services Datadog, Prometheus, Stackdriver, SignalFx, or New Relic using their metrics for canary analysis

Deploy across multiple cloud providers including AWS EC2, Kubernetes, Google Compute Engine, Google Kubernetes Engine, Google App Engine, Microsoft Azure, Openstack, Cloud Foundry, Oracle Cloud Infrastructure, and DC/OS

Trigger pipelines via git events, Jenkins, Travis CI, Docker, CRON, or other Spinnaker pipelines

Set up event notifications for email, Slack, HipChat, or SMS (via Twilio)

Restrict the execution of stages to certain windows of time, making sure deployments happen during off-peak traffic or when the right people are on hand to monitor the roll-out

Restrict access to projects or accounts by hooking into your internal authentication system using OAuth, SAML, LDAP, X.509 certs, Google Groups, Azure Groups, or GitHub Teams

Test that your application can survive instance failures by terminating them on purpose