Building the demo app
In this lab you will push the changes to your origin repository and verify that the pipeline has successfully finished both in GitLab and by checking the image in Amazon ECR.
- Return to the browser tab with Cloud9 and execute the following command in the terminal. Specify
rootas the username and the same password you used in Create a GitLab repository to log in to GitLab:
git push -u origin main
- Return to the browser tab with GitLab and in the navigation pane choose CI/CD > Pipelines.
- Make sure that the CI/CD pipeline is successfully completed or wait until it does. If there were any issues, open the failed stage by clicking the corresponding circle and check the detailed execution log:
- Return to the browser tab with AWS Console.
- Type
ECRin the search box at the top and open the Elastic Container Registry service. - Open the repository with gitlab-spot-demo in its name and verify that it contains an image that has just been built in GitLab:
You have successfully built the image and can now proceed to Deploying Amazon EKS on Spot instances.
Challenges
If this and previous sections of the workshop seemed too easy, try completing the following challenges:
Challenge 1: Configure shared runners for the whole GitLab CI/CD and not just the current repository. Create an additional repository and verify that your runners serve it too.
Open the Admin Area of GitLab interface and in the Runners section get the registration code. Use it instead of the one from the project.
Challenge 2: Trigger auto-scaling of the instances to get more runners created.
By default, auto-scaling is done by CPU load, so you can run a CPU load generator inside your build scripts to simulate it, for example, you can use stress or stress-ng tools for this.
Challenge 3: Modify the auto-scaling group to perform scaling by the number of the jobs instead of the CPU load.
Create a Lambda function that gets the number of jobs from GitLab API and publishes it as a custom CloudWatch metric. Use this metric to scale the group.