CI / CD with Kubernetes on AWS for a sample Java project

A walkthrough of a Continuous Delivery / Continuous Integration pipelines
for a sample Java project https://github.com/romanastr/base-gradle-cicd.
00:00 - Introduction
00:40 - Project Overview
05:28 - Infrastructure as Code (IaC) idea
07:31 - AWS Cloud Platform
09:57 - Build with Gradle in Kotlin DSL
15:19 - Infrastructure as code with Ansible and AWS CloudFormation
19:07 - Build Infrastructure Choices - Jenkins vs AWS native
23:47 - Native AWS Build tools - CodeBuild, CodePipeline, ECR
28:01 - Integration with GitHub
32:15 - Options for deploying containers in AWS
34:10 - Managed Kubernetes on AWS (EKS)
37:59 - Cost Reduction
41:24 - Gradle Distributed Cache
43:42 - Conclusions

The project consists of 3 interacting apps build with Gradle. Definitions of application infrastructure and build infrastructure are created as code and deployed to AWS cloud platform. Apps are deployed with managed Kubernetes service (EKS) on AWS. Build infrastructure is created with native AWS build tools CodeBuild and CodePipeline. Full integration with GitHub triggers and status checks is demonstrated. PR and CI pipelines vet changes on building code, unit tests, deployment of infrastructure and app containers into test environments, and load tests on top of the deployed components. Distributed Gradle cache is created to further accelerate builds. A total of 16 different AWS services is utilized overall.

Authored by Roman Shcherbakov, a Software Architect at Bandwidth: https://www.linkedin.com/in/shcher/.
Website: https://astroman.org.