CDK BlueGreen Deployment Codepipeline Pattern #181
Conversation
| errorHandler(app, "Blue Green cluster pattern is not setup. It may be due to missing secrets: ", error); | ||
| }); | ||
|
|
||
| // import { configureApp, errorHandler } from '../lib/common/construct-utils'; |
There was a problem hiding this comment.
let's remove commented code. applies elsewhere.
| envName: string; | ||
| } | ||
|
|
||
| class DnsStack extends cdk.Stack { |
There was a problem hiding this comment.
add comments on top, explain the purpose for this stack
| import * as blueprints from '@aws-quickstart/eks-blueprints'; | ||
|
|
||
|
|
||
| export default class MultiClusterBuilderConstruct { |
There was a problem hiding this comment.
what makes it multi-cluster? Seems like it create a common blueprint. General approach on using this is using a function for example. Here is code example, mostly pseudo:
const clusterBlueprint = buildCommonBlueprint();
const blueClusterBlueprint = clusterBlueprint.clone(); // if you plan to customize, like adding additional addons, change providers
const greenClusterBlueprint = blueClusterBlueprint.clone(); // if you plan to customizeYou can even inline the function. Having a separate class maybe an overkill - does not buy us much. Maybe keep the file, like common-builder.ts and put one builder function in it.
| stackBuilder : blueprintBlue.clone(region), | ||
| // stageProps: { | ||
| // post: [ | ||
| // new ShellStep("Validate App", { |
There was a problem hiding this comment.
why validation is commented out? did it work?
| // } | ||
| }) | ||
|
|
||
| const blueprintGreen = blueprintBuilder |
There was a problem hiding this comment.
why version and cluster provider are here and not in the blueprint?
| const stagesEks : blueprints.StackStage[] = []; | ||
|
|
||
| const blueprintBuilder = new MultiClusterBuilderConstruct().create(scope, accountID, region); | ||
| const blueprintBlue = blueprintBuilder |
There was a problem hiding this comment.
why version and cluster provider are here and not in the common blueprint?
| }) | ||
| const stagesDns : blueprints.StackStage[] = []; | ||
|
|
||
| const prodEnv = clusterBNameSuffix; |
There was a problem hiding this comment.
let's say switch worked and moved DNS target to green. Now I have blue/green, Route53 points to green. What happens on the next iteration, when customer upgrades clusters to 1.31 and needs to engage blue/green again. Do you change the name of prodEnv?
Issue #, if available:
Description of changes: Created a new pattern that supports 2 versions of EKS clusters i.e. blue and green simultaneously running. The switching from Blue to Green and vice-versa is done by updating the DNS record which requires manual approval in codepipeline.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.