stelligent / mu

A full-stack DevOps on AWS framework
https://getmu.io
MIT License
973 stars 135 forks source link

Map deployment strategy to eks #375

Closed BennyHarv3 closed 5 years ago

BennyHarv3 commented 5 years ago

Closes #359.

Functional testing of each strategy complete. There is an issue where you can't change your deployment strategy from blue_green or rolling to replace after the EKS cluster has been created (and likely vice versa, didn't check), but I don't expect it to be much of a problem. Changing from blue_green to rolling and back works fine.

BennyHarv3 commented 5 years ago

As a heads up, whenever When #345 occurs, it causes the ELB generated by EKS to not be cleaned up properly. The workflow where I encountered it:

  1. Run make e2e_eks to start the test run
  2. Issue #345 occurs part way through the Deploy CodeBuild project.
  3. Manually enable the KMS key.
  4. Rerun the final section of the CodePipeline to get everything to pass.
  5. Run mu purge.

mu purge fails on the VPC stack because the VPC has dependencies. The only way I was able to get mu purge to continue on is manually deleting the ELB, manually deleting the VPC, and then manually deleting the CloudFormation stack.