DevOps with Claude Code: Terraform, EKS, ArgoCD & Helm

Run all eight microservices locally with Docker Compose to see the pet clinic in action. Set up cloud code and begin Terraform with remote state using S3 and DynamoDB.

Run eight microservices with docker compose up -d, enforcing startup order via config and discovery servers and health checks, with api gateway and observability through Eureka, Zipkin, Prometheus, and Grafana.

Master the Jira board workflow to pick epics and tickets, read the technical spec, and drive cloud code builds from Terraform foundations to remote state and GitOps with Argo CD.

Connect Claude Code to Jira via Atlassian mcp, authenticate with OAuth, and generate five pet clinic platform stories (directory structure, bootstrap, backends, providers, versions) with terraform init, validate, and fmt.

Explore building a full public VPC with two public subnets across two availability zones, an internet gateway, and security groups, mapping public IPs for EKS, dev, and prod.

Compare the all-public-subnet production design with the learning setup, using security groups as the perimeter, ADR-0001, and cost savings from no nat gateway.

Build a complete reusable vpc module with four security groups, subnets, and igw in dev and prod using cloud code. Experience agentic workflow with automatic review, terraform validate, and hooks.

Execute a safe terraform deployment workflow by planning with plan dev, reviewing the plan, and applying to create real aws resources, handle errors, and store state in s3.

Build and configure an Amazon EKS cluster with managed node groups and OIDC integration using IRSA, including Core DNS, kube proxy, VPC CNI, and the EBS CSI driver.

Build the entire EKS module with Cloud Code, implementing cluster and IAM roles, node groups, kubectl access, and add-ons, then validate and review for security and best practices.

Review and deploy the EKS module by validating IAM trust policies, OIDC/IRSA setup, and add-on versions, then run terraform plan and apply to provision resources.

Leverage a Terraform module to build eight private ECR repositories for dev and prod, enabling scan on push, lifecycle policies, and tag immutability, with ARM64 docker images for Graviton EKS.

Verify eight ECR repositories in the petclinic-dev-namespace, confirm v1.0.0 images and scan-on-push results, and assess CVEs to maintain a secure, repeatable build workflow.

Set up a shared RDS MySQL on db.t4g.micro for the pet clinic apps, with Terraform-generated credentials in Secrets Manager and secure access from the EKS cluster.

Review the RDS module and credential flow, ensure security group, parameter group, and lifecycle settings align across dev and prod, then deploy and collect the RDS endpoint.

Verify connectivity from a debug pod inside the cluster to the RDS MySQL instance, validate credentials from Secrets Manager, and confirm utf-8mb4 parameter group is applied.

Build the entire DNS and ingress stack for EKS using Terraform and Helm. Configure Route 53 hosted zone, ALB ingress, DNS records, and dev environment wiring with validation.

Review and deploy the dns, certificate validation, and ingress settings across two phases, ensuring proper data source hosted zone usage, acm validation, and accurate ingress annotations for a secure alb.

Verify the infrastructure by performing four checks: DNS resolution via Route 53, ACM certificate validation, ALB ingress, and HTTPS access in the browser; implemented with Terraform, Helm, and Kubernetes.

Explore end-to-end secrets management with AWS Secrets Manager, IRSA, and the External Secrets Operator, as secrets flow from AWS to Kubernetes secrets and into pod environments.

Verify end-to-end secret management from AWS secrets manager to Kubernetes, ensuring ESO health, synced external secrets, and decoded values match across RDS credentials and OpenAI API key.

Deploy eight services to Kubernetes using base manifests and overlays, with four files per service, init containers, and health probes ensuring startup order from config server to discovery server.

Verify that all eight pods and services are up, reachable, and end-to-end functional from browser to database through the ALB, API gateway, Eureka, and RDS.

Explain helm chart anatomy and why helm, replacing yaml files with templates and helpers. Describe the values merge order, chart defaults, per environment, then per service—and Argo CD's GitOps workflow.

Build with Claude Code by converting the plane yaml into a helm chart, templating deployments, services, and config maps, with per service and environment values, and validate with helm lint.

Review and deploy with helm upgrade --install, verify templates and values merge, then deploy in startup order from config server to all services, validating rds endpoints and secrets.