Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 36,969
    • Issues 36,969
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,454
    • Merge requests 1,454
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #35409

Closed
Open
Created Nov 01, 2019 by Orit Golowinski@ogolowinskiDeveloper

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 image

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

Edited Nov 01, 2019 by Orit Golowinski
Assignee
Assign to
Backlog
Milestone
Backlog
Assign milestone
Time tracking