One of the key sub-areas within Continuous Delivery that we're tracking is incremental rollout. This is important because it enables unprecedented control over how you deliver your software in a safe way. For these items we're also tagging the label "incremental rollout", and you can see an issue list of these items here. Incremental rollout also serves as a key pillar for our Progressive Delivery strategy.
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 type is a very simple deployment, 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.
TBD
TBD
TBD
TBD
TBD
TBD
TBD
