The following 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.
Advanced deployment techniques help teams control the deployment of new software versions as well as the rollout of new features to users. This includes the ability to release features to a limited audience, monitor the performance and behavior, and make a conscious decision whether to continue the rollout or if needed, to rollback.
GitLab Advanced Deployments enable organizations to leverage sophisticated deployment techniques to enable frequent and safe deployments to production. Enterprises using GitLab for software development can easily use solutions such as blue/green deployments, canary releases, and other methods to deploy to production with confidence while minimizing negative impact to users and rolling back as needed.
Create two (nearly) identical environments, arbitrarily called blue and green. One isn't better than the other, just separate. With all traffic going to green, load new code onto blue, get it ready, and then switch the router to suddenly, as quickly as possible, send all new traffic to blue.
This is a very simple deployment where all of the old pods are killed and replaced all at once with the new ones.
In a Canary Release, you start with all your machines/dockers/pods at 100% of the current deployment. When you are ready to try out your new deployment on a subset of your users, you send those user's traffic to the new deployment, while the others are still on the current one. The terms canary release and incremental release are very similar and often used interchangeably.
We are currently working on bug fixes and UX improvements. If there are specific issues that you are interested in, please upvote the issue and/or leave feedback on the issue itself.
This category is currently at the "Viable" maturity level, and our next maturity target is Complete (see our definitions of maturity levels).
Our most popular customer issue is gitlab#25629 which expands our deploy boards to support stateful sets as well in addition to deployment replica sets.
Our top vision item is gitlab#226994 which introduces advanced deployments for non-Kubernetes users.