~/ nmadiraju.com Amazon EKS · Progressive delivery
arrow_back Back to nmadiraju
Visual Walkthrough · Delivery and operations

How Progressive Delivery Works on Amazon EKS

Follow the checkout service shipping v2 with Argo Rollouts, ALB weights and Prometheus, then check yourself with 8 questions.

1Visual Walkthrough

Argo Rollouts shipping checkout v2 on EKS through ALB weighted target groups, with Prometheus analysis and Argo CD Left, a Git repo and the shoppers. Next, a VPC with an ALB that forwards to two target groups by weight. Right, EKS cluster shop-prod: Argo CD, the Argo Rollouts controller, the AWS Load Balancer Controller and Prometheus, and namespace checkout with the Rollout, an AnalysisRun, the Ingress, stable and canary Services and ReplicaSets. The walkthrough replaces a rolling update with canary steps, uses ALB weights, aborts a bad version on a failed analysis, and shows Argo CD's view after an abort and during a pause. Git acme/platform-config apps/checkout/ Shoppers shop.example.com VPC ALB HTTPS :443 · /checkout forward, by weight: target type: ip EKS CLUSTER shop-prod · us-east-1 NS ARGOCD Application checkout · auto-sync NS ARGO-ROLLOUTS Argo Rollouts controller runs the steps, sets the weights, starts analysis NS KUBE-SYSTEM LB Controller AWS Load Balancer Controller Ingress → ALB rules and target groups NS MONITORING Prometheus scrapes checkout Pods http_requests_total by code, by version NS CHECKOUT Deployment checkout replicas: 10 strategy: RollingUpdate maxSurge 25% · maxUnavail. 25% Rollout checkout replicas: 10 · canary AnalysisRun error-rate Ingress checkout

    2Quiz to check understanding

    Check yourself