Safe Continuous Deployment with Blue-Green Deployment - #2978
Conversation
ericcornelissen
left a comment
There was a problem hiding this comment.
Thank you for the proposal, it looks good but please add a description of what you plan to do in the demo in addition to a description of what blue-green deployments are.
Also, please mark your pull request as ready for review so we can merge it.
|
Readme is not correctly formatted Got: ['Assignment Proposal', 'Title', 'Names and KTH ID', 'Deadline', 'Category', 'Description', 'Relevance'] |
2 similar comments
|
Readme is not correctly formatted Got: ['Assignment Proposal', 'Title', 'Names and KTH ID', 'Deadline', 'Category', 'Description', 'Relevance'] |
|
Readme is not correctly formatted Got: ['Assignment Proposal', 'Title', 'Names and KTH ID', 'Deadline', 'Category', 'Description', 'Relevance'] |
ericcornelissen
left a comment
There was a problem hiding this comment.
Thank you for updating the proposal, it looks good now 👍
Assignment Proposal
Title
Safe Continuous Deployment with Blue-Green Deployment
Names and KTH ID
Deadline
Category
Description
Blue-green deployment is a release strategy that uses two identical production environments: one active environment serving users and one inactive environment. A new application version is deployed to the inactive environment and tested before production traffic is redirected to it. If the checks fail, the active environment continues serving traffic. If problems appear after the switch, traffic can quickly be redirected to the previous environment.
During the demo, deployed in Killercoda we will show a simple Continuous Deployment pipeline that:
This will allow us to compare successful and unsuccessful deployments and show how blue-green deployment can reduce downtime and deployment risk.
Relevance
Continuous Deployment is an important DevOps practice for releasing changes quickly and safely. This demo illustrates how automated validation, failure handling, traffic switching, and rollback can reduce production downtime and prevent faulty releases from reaching users.