1.
Introduction
1.1 Prerequisites
2.
Repos & Helm chart
2.1 Create 3 GitHub repos
2.2 Generate Helm chart with AI
2.3 Customize values & ingress
3.
CI - SonarQube
3.1 Initialize source code
3.2 Create SonarQube server (EC2)
3.3 Log in & create token
3.4 sonar-project.properties
4.
Registry, access & notify
4.1 Create ECR repository
4.2 Create CI IAM user
4.3 Slack app & webhook
5.
GitHub PAT & Secrets
5.1 Create GitHub PAT
5.2 Store GitHub Secrets
5.3 Store GitHub Variables
6.
CI/CD Pipeline
6.1 Create a feature branch
6.2 Generate pipeline with AI
6.3 Review the pipeline
7.
Run pipeline via PR
7.1 Commit the pipeline
7.2 Update SONAR_HOST_URL
7.3 Raise a Pull Request
7.4 Check the Quality Gate
7.5 Merge & run Docker + Helm
7.6 Verify the result
8.
EKS prerequisites
8.1 Domain & certificate
8.2 Install local tools
8.3 Administrator IAM user
8.4 aws configure
9.
EKS with Terraform
9.1 Open repo & AI coding
9.2 Generate Terraform EKS
9.3 Review & apply
9.4 EBS CSI Driver
10.
ALB Controller & ArgoCD
10.1 AWS LB Controller
10.2 Install ArgoCD
10.3 Ingress for ArgoCD
10.4 Configure DNS
10.5 Access ArgoCD
11.
ArgoCD syncs vProfile
11.1 Login & add Git repo
11.2 ECR access for nodes
11.3 Commit Terraform
11.4 ArgoCD manifests
11.5 Apply & verify
12.
Access & test
12.1 DNS for the app
12.2 Access the app
12.3 Test the GitOps loop
13.
Clean Up
14.
Summary
Tiếng Việt
English
AWS Cloud Clubs Việt Nam
Last Updated
2026
Author
Kiet Tran
vProfile GitOps Workshop
> CI - SonarQube
CI - SonarQube
Code quality analysis with SonarQube
Stand up a SonarQube server on EC2 and prepare the config so the pipeline can push analysis results.
3.1 Initialize source code
3.2 Create SonarQube server (EC2)
3.3 Log in & create token
3.4 sonar-project.properties