This is self-paced workshop designed to allow developers and system administrators to get hands on with Amazon Elastic Container Service concepts such as service and container-instance auto-scaling, spot-fleet integration, container placement strategies, service discovery, secrets management with AWS Systems Manager Parameter Store, time-based and event-based scheduling, and automated deployment pipelines.
Apache License 2.0
167
stars
72
forks
source link
Lab to demonstrate how container healthchecks improve reliability of deployments. #21
After the deployment pipeline has been configured, a health check should be added to the task definition for the dogs application. The health check should test for the presence of particular file (for example, 1.jpg).
From the IDE, the Dockerfile is intentionally modified to ensure the dog memes don't get pulled in to the image at build time.
The changes are then committed and the pipeline will build the new image and attempt to deploy. Based on the roll out configuration of the dogs service. The new version of dogs, with the missing images, should not make it in to production, the deployment should fail, but their should be at least 50% of the current dogs containers still running, ensuring that there is no loss of service.
After the deployment pipeline has been configured, a health check should be added to the task definition for the dogs application. The health check should test for the presence of particular file (for example, 1.jpg).
From the IDE, the Dockerfile is intentionally modified to ensure the dog memes don't get pulled in to the image at build time.
The changes are then committed and the pipeline will build the new image and attempt to deploy. Based on the roll out configuration of the dogs service. The new version of dogs, with the missing images, should not make it in to production, the deployment should fail, but their should be at least 50% of the current dogs containers still running, ensuring that there is no loss of service.