eks-deployment

What problem does it solve?

Deploying a cloud-native, Spring Boot banking platform to AWS EKS requires coordinating cluster bootstrap, IAM/IRSA, secrets, ingress/tls, autoscaling, storage, and safe Helm rollouts; this Skill encapsulates those operational patterns to minimize downtime and security risk during production deployments.

Core Features & Use Cases

• Cluster bootstrap: eksctl cluster configuration for managed node groups, addons (vpc-cni, coredns, kube-proxy), and CloudWatch logging to create a resilient multi-AZ cluster.
• Pod-level IAM & secret management: IRSA setup and External Secrets Operator integration with AWS Secrets Manager for least-privilege access and automated secret sync.
• Ingress, TLS & DNS: AWS Load Balancer Controller (ALB) with ACM certificates and ExternalDNS annotations for automated Route53 records and WAF integration.
• Resilience & autoscaling: Helm-driven deployments with HPA, PodDisruptionBudget, Cluster Autoscaler / Karpenter guidance, topology spread and taints/labels for AZ spreading and workload isolation.
• CI/CD & safe rollouts: Helm values production overrides, atomic upgrades, rollout verification, and a deploy script for GitHub Actions to enforce health checks and automatic rollback.
• Use Case: Safely deploy and operate the banking platform in production with zero-downtime upgrades, secure secret access, and automated TLS and DNS management.

Quick Start

Deploy the banking platform to a production EKS cluster by applying the provided eksctl cluster.yaml, installing External Secrets and the AWS Load Balancer Controller, and performing a Helm upgrade --install of the helm/banking-platform chart with the production values file.