Creating a staging CodePipeline project with mesh deployment and chaos testing with AWS FIS
In the previous section, we deployed the microservices in the catalogapp-dev
EKS cluster using the CatalogApp-DevBuild
CodePipeline project. This CodePipeline project also sent the latest image version to Parameter Store, which can be referenced in the staging CodePipeline project. The staging CodePipeline project will fetch the image version and try to compare it with the existing running image as deployment
in the catalogapp-staging
EKS cluster. If the image versions are different, then the image version present in Parameter Store will be updated in the deployment of the catalogapp-staging
EKS cluster. If the image is not present in the catalogapp-staging
EKS cluster, then it will deploy the new service with the latest image present in Parameter Store.
Once the service is up and running, then the next stage will be resiliency testing on the EKS cluster using an AWS FIS experiment template...