Keep Environment in standby for a limited time after new deployment is rolled out

Problem to solve

Even if all the tests pass and the deployment to production was successful, there might be a serious problem that was undetected and require a fast rollback to the previous deployment. (Can also be thought about as Blue/Green deployment)

Intended users

• DevOps Engineers
• Developers
• Release Managers

Further details

Spinnaker already supports this functionality

Proposal

Do not tear down the previous environment even if there is a successful deployment to production environment (protected environments)

For the MVP we will set this configuration to 3 days and it cannot be changed by the user. In a later stage we will add settings so the user can define the standby period to leave the environment alive.

The standby environment can be accessed by the user at this time similar to a review app but the production environment will have the newest deployment.

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references

https://blog.spinnaker.io/introducing-rollout-strategies-in-the-kubernetes-v2-provider-8bbffea109a

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.