Architecture of Continuous Delivery Pipeline Using Docker Kubernetes Aws

Build a Continuous Delivery Pipeline for Your Container Images with Amazon ECR as Source

Today, we are launching support for Amazon Elastic Container Registry (Amazon ECR) as a source provider in AWS CodePipeline. You can now initiate an AWS CodePipeline pipeline update by uploading a new image to Amazon ECR. This makes it easier to set up a continuous delivery pipeline and use the AWS Developer Tools for CI/CD.

You can use Amazon ECR as a source if you're implementing a blue/green deployment with AWS CodeDeploy from the AWS CodePipeline console. For more information about using the Amazon Elastic Container Service (Amazon ECS) console to implement a blue/green deployment without CodePipeline, see Implement Blue/Green Deployments for AWS Fargate and Amazon ECS Powered by AWS CodeDeploy.

This post shows you how to create a complete, end-to-end continuous deployment (CD) pipeline with Amazon ECR and AWS CodePipeline. It walks you through setting up a pipeline to build your images when the upstream base image is updated.

Prerequisites

To follow along, you must have these resources in place:

• A source control repository with your base image Dockerfile and a Docker image repository to store your image. In this walkthrough, we use a simple Dockerfile for the base image:

    FROM alpine:3.8      RUN apk update      RUN apk add nodejs

• A source control repository with your application Dockerfile and source code and a Docker image repository to store your image. For the application Dockerfile, we use our base image and then add our application code:

    FROM 012345678910.dkr.ecr.us-east-1.amazonaws.com/base-image      ENV PORT=80      EXPOSE $PORT      COPY app.js /app/      CMD ["node", "/app/app.js"]

This walkthrough uses AWS CodeCommit for the source control repositories and Amazon ECR  for the Docker image repositories. For more information, see Create an AWS CodeCommit Repository in the AWS CodeCommit User Guide and Creating a Repository in the Amazon Elastic Container Registry User Guide.

Note: The source control repositories and image repositories must be created in the same AWS Region.

Set up IAM service roles

In this walkthrough you use AWS CodeBuild and AWS CodePipeline to build your Docker images and push them to Amazon ECR. Both services use Identity and Access Management (IAM) service roles to makes calls to Amazon ECR API operations. The service roles must have a policy that provides permissions to make these Amazon ECR calls. The following procedure helps you attach the required permissions to the CodeBuild service role.

To create the CodeBuild service role

1. Follow these steps to use the IAM console to create a CodeBuild service role.
2. On step 10, make sure to also add the AmazonEC2ContainerRegistryPowerUser policy to your role.

Create a build specification file for your base image

A build specification file (or build spec) is a collection of build commands and related settings, in YAML format, that AWS CodeBuild uses to run a build. Add a buildspec.yml file to your source code repository to tell CodeBuild how to build your base image. The example build specification used here does the following:

• Pre-build stage:
  • Sign in to Amazon ECR.
  • Set the repository URI to your ECR image and add an image tag with the first seven characters of the Git commit ID of the source.
• Build stage:
  • Build the Docker image and tag the image with latest and the Git commit ID.
• Post-build stage:
  • Push the image with both tags to your Amazon ECR repository.

version: 0.2  phases:   pre_build:     commands:       - echo Logging in to Amazon ECR...       - aws --version       - $(aws ecr get-login --region $AWS_DEFAULT_REGION --no-include-email)       - REPOSITORY_URI=012345678910.dkr.ecr.us-east-1.amazonaws.com/base-image       - COMMIT_HASH=$(echo $CODEBUILD_RESOLVED_SOURCE_VERSION | cut -c 1-7)       - IMAGE_TAG=${COMMIT_HASH:=latest}   build:     commands:       - echo Build started on `date`       - echo Building the Docker image...       - docker build -t $REPOSITORY_URI:latest .       - docker tag $REPOSITORY_URI:latest $REPOSITORY_URI:$IMAGE_TAG   post_build:     commands:       - echo Build completed on `date`       - echo Pushing the Docker images...       - docker push $REPOSITORY_URI:latest       - docker push $REPOSITORY_URI:$IMAGE_TAG

To add a buildspec.yml file to your source repository

1. Open a text editor and then copy and paste the build specification above into a new file.
2. Replace the REPOSITORY_URI value (012345678910.dkr.ecr.us-east-1.amazonaws.com/base-image) with your Amazon ECR repository URI (without any image tag) for your Docker image. Replace base-image with the name for your base Docker image.
3. Commit and push your buildspec.yml file to your source repository.

            git add .     git commit -m "Adding build specification."     git push

Create a build specification file for your application

Add a buildspec.yml file to your source code repository to tell CodeBuild how to build your source code and your application image. The example build specification used here does the following:

• Pre-build stage:
  • Sign in to Amazon ECR.
  • Set the repository URI to your ECR image and add an image tag with the first seven characters of the CodeBuild build ID.
• Build stage:
  • Build the Docker image and tag the image with latest and the Git commit ID.
• Post-build stage:
  • Push the image with both tags to your ECR repository.

version: 0.2  phases:   pre_build:     commands:       - echo Logging in to Amazon ECR...       - aws --version       - $(aws ecr get-login --region $AWS_DEFAULT_REGION --no-include-email)       - REPOSITORY_URI=012345678910.dkr.ecr.us-east-1.amazonaws.com/hello-world       - COMMIT_HASH=$(echo $CODEBUILD_RESOLVED_SOURCE_VERSION | cut -c 1-7)       - IMAGE_TAG=build-$(echo $CODEBUILD_BUILD_ID | awk -F":" '{print $2}')   build:     commands:       - echo Build started on `date`       - echo Building the Docker image...       - docker build -t $REPOSITORY_URI:latest .       - docker tag $REPOSITORY_URI:latest $REPOSITORY_URI:$IMAGE_TAG   post_build:     commands:       - echo Build completed on `date`       - echo Pushing the Docker images...       - docker push $REPOSITORY_URI:latest       - docker push $REPOSITORY_URI:$IMAGE_TAG artifacts:   files:     - imageDetail.json

To add a buildspec.yml file to your source repository

1. Open a text editor and then copy and paste the build specification above into a new file.
2. Replace the REPOSITORY_URI value (012345678910.dkr.ecr.us-east-1.amazonaws.com/hello-world) with your Amazon ECR repository URI (without any image tag) for your Docker image. Replace hello-world with the container name in your service's task definition that references your Docker image.
3. Commit and push your buildspec.yml file to your source repository.

            git add .     git commit -m "Adding build specification."     git push

Create a continuous deployment pipeline for your base image

Use the AWS CodePipeline wizard to create your pipeline stages:

1. Open the AWS CodePipeline console at https://console.aws.amazon.com/codepipeline/.
2. On the Welcome page, choose Create pipeline.
   If this is your first time using AWS CodePipeline, an introductory page appears instead of Welcome. Choose Get Started Now.
3. On the Step 1: Name page, for Pipeline name, type the name for your pipeline and choose Next step. For this walkthrough, the pipeline name is base-image.
4. On the Step 2: Source page, for Source provider, choose AWS CodeCommit.
   1. For Repository name, choose the name of the AWS CodeCommit repository to use as the source location for your pipeline.
   2. For Branch name, choose the branch to use, and then choose Next step.
5. On the Step 3: Build page, choose AWS CodeBuild, and then choose Create project.
   1. For Project name, choose a unique name for your build project. For this walkthrough, the project name is base-image.
   2. For Operating system, choose Ubuntu.
   3. For Runtime, choose Docker.
   4. For Version, choose aws/codebuild/docker:17.09.0.
   5. For Service role, choose Existing service role, choose the CodeBuild service role you've created earlier, and then clear the Allow AWS CodeBuild to modify this service role so it can be used with this build project box.
   6. Choose Continue to CodePipeline.
   7. Choose Next.
6. On the Step 4: Deploy page, choose Skip and acknowledge the pop-up warning.
7. On the Step 5: Review page, review your pipeline configuration, and then choose Create pipeline.

Create a continuous deployment pipeline for your application image

The execution of the application image pipeline is triggered by changes to the application source code and changes to the upstream base image. You first create a pipeline, and then edit it to add a second source stage.

1. 1. Open the AWS CodePipeline console at https://console.aws.amazon.com/codepipeline/.
   2. On the Welcome page, choose Create pipeline.
   3. On the Step 1: Name page, for Pipeline name, type the name for your pipeline, and then choose Next step. For this walkthrough, the pipeline name is hello-world.
   4. For Service role, choose Existing service role, and then choose the CodePipeline service role you modified earlier.
   5. On the Step 2: Source page, for Source provider, choose Amazon ECR.
      1. For Repository name, choose the name of the Amazon ECR repository to use as the source location for your pipeline. For this walkthrough, the repository name is base-image.

1. On the Step 3: Build page, choose AWS CodeBuild, and then choose Create project.
   1. For Project name, choose a unique name for your build project. For this walkthrough, the project name is hello-world.
   2. For Operating system, choose Ubuntu.
   3. For Runtime, choose Docker.
   4. For Version, choose aws/codebuild/docker:17.09.0.
   5. For Service role, choose Existing service role, choose the CodeBuild service role you've created earlier, and then clear the Allow AWS CodeBuild to modify this service role so it can be used with this build project box.
   6. Choose Continue to CodePipeline.
   7. Choose Next.
2. On the Step 4: Deploy page, choose Skip and acknowledge the pop-up warning.
3. On the Step 5: Review page, review your pipeline configuration, and then choose Create pipeline.

The pipeline will fail, because it is missing the application source code. Next, you edit the pipeline to add an additional action to the source stage.

1. Open the AWS CodePipeline console at https://console.aws.amazon.com/codepipeline/.
2. On the Welcome page, choose your pipeline from the list. For this walkthrough, the pipeline name is hello-world.
3. On the pipeline page, choose Edit.
4. On the Editing: hello-world page, in Edit: Source, choose Edit stage.
5. Choose the existing source action, and choose the edit icon.
   1. Change Output artifacts to BaseImage, and then choose Save.
6. Choose Add action, and then enter a name for the action (for example, Code).
   1. For Action provider, choose AWS CodeCommit.
   2. For Repository name, choose the name of the AWS CodeCommit repository for your application source code.
   3. For Branch name, choose the branch.
   4. For Output artifacts, specify SourceArtifact, and then choose Save.
7. On the Editing: hello-world page, choose Save and acknowledge the pop-up warning.

Test your end-to-end pipeline

Your pipeline should have everything for running an end-to-end native AWS continuous deployment. Now, test its functionality by pushing a code change to your base image repository.

1. Make a change to your configured source repository, and then commit and push the change.
2. Open the AWS CodePipeline console at https://console.aws.amazon.com/codepipeline/.
3. Choose your pipeline from the list.
4. Watch the pipeline progress through its stages. As the base image is built and pushed to Amazon ECR, see how the second pipeline is triggered, too. When the execution of your pipeline is complete, your application image is pushed to Amazon ECR, and you are now ready to deploy your application. For more information about continuously deploying your application, see Create a Pipeline with an Amazon ECR Source and ECS-to-CodeDeploy Deployment in the AWS CodePipeline User Guide.

Conclusion

In this post, we showed you how to create a complete, end-to-end continuous deployment (CD) pipeline with Amazon ECR and AWS CodePipeline. You saw how to initiate an AWS CodePipeline pipeline update by uploading a new image to Amazon ECR. Support for Amazon ECR in AWS CodePipeline makes it easier to set up a continuous delivery pipeline and use the AWS Developer Tools for CI/CD.

schauerwiclactustob.blogspot.com

Source: https://aws.amazon.com/blogs/devops/build-a-continuous-delivery-pipeline-for-your-container-images-with-amazon-ecr-as-source/