Centralized log of all issues encountered, grouped by category, including root causes and resolutions.
VpcLimitExceeded
❌ Too many VPCs in the account
✅ Resolved by deleting unused VPCs via AWS Console.
Duplicate Variable Declaration
❌ cluster_name declared twice in variables.tf
✅ Removed the duplicate block.
Invalid Cluster Name Format
❌ Used a cluster name with unsupported characters
✅ Renamed to production-eks-cluster (letters, numbers, dashes allowed).
Missing S3 Backend
❌ Terraform failed due to missing backend config
✅ Created S3 bucket and DynamoDB table via AWS Console, then added backend.tf.
Missing Cluster Name for EKS Auth
❌ aws eks update-kubeconfig --name failed
✅ Added the correct cluster_name as a GitHub variable.
Unauthorized Docker Login
❌ Failed to authenticate with ECR
✅ Fixed by correcting ECR_REPO variable and checking image naming.
Nothing to Commit Error
❌ GitHub Action failed after pushing manifest with no changes
✅ This is a harmless message when no updates are detected.
Kubernetes / Argo CD Issues
❌ InvalidSpecError: Missing Namespace
Error:
Namespace for bank-backend-deployment apps/v1, Kind=Deployment is missing.
Fix: Added namespace: default explicitly in the deploy.yaml.
❌ CrashLoopBackOff on Backend Pod
Error: Pod kept restarting due to failure inside the container.
Root Cause:
The MySQL connection URL in application.properties inside the src/main/resources/ directory was incorrect. It pointed to a wrong DB host, leading to failed DB initialization and app crash.
Fix:
Updated the MySQL spring.datasource.url property to use the correct RDS endpoint, matching the DB host in the deployed RDS instance.
Example fix:
spring.datasource.url=jdbc:mysql://<correct-db-host>:3306/bank_db
❌ Back-off Restarting Failed Container
Symptom:
Argo CD showed the error Back-off restarting failed container bank-backend-container in the pod.
Resolution:
After updating application.properties and pushing changes, the app deployed successfully.