Automate the production lifecycle

This is the final step of https://gitlab.com/gitlab-com/infrastructure/issues/1210.

Production deployments need to be automated and should be able to easily move to different git tags/branches.

mentioned in issue #1210 (closed)

This is important to figure out since it causes a lot of downtime and toil, https://gitlab.com/gitlab-com/infrastructure/issues/1365

@omame made a "new" deployment procedure, https://gitlab.com/gitlab-com/infrastructure/issues/1365#note_26004822

What is the future of that?

How does this relate to https://gitlab.com/gitlab-com/infrastructure/issues/1386 ?

@ernstvn this relates in the way that we get rid of our current deployment procedure by automating deployments and the production lifecycle in general by leveraging an orchestration tool.

The future of the "new" deployment procedure (that is just a recovery from the old including the changes in the fleet structure) is to die as soon as possible.

We are working this in takeoff now.

Closing as this issue is not really actionable as it is and there are ongoing efforts.

closed

removed milestone

mentioned in issue #3523 (closed)