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

How Flux Works on Amazon EKS

Follow web and cert-manager from repo acme/fleet into an EKS cluster through Flux, then check yourself with 8 questions.

1Visual Walkthrough

Flux controllers in an EKS cluster applying the web app and cert-manager from a Git repository Left, a platform engineer, an on-call engineer and a Slack channel. Next, the Git repo acme/fleet with clusters/prod, infra and apps/web files. Right, EKS cluster shop-prod: namespace flux-system with source-controller, kustomize-controller, helm-controller and notification-controller, then namespaces cert-manager and web. The walkthrough bootstraps Flux, ships a new tag, reverts a hand edit, prunes a deleted file, orders cert-manager before the app with dependsOn, and rolls back a failed Helm upgrade. Priya · platform merges PRs to main Sam · on-call has kubectl access Slack #platform Flux alerts land here GIT · acme/fleet clusters/prod/ flux-system/ · Flux itself Flux Kustomization objects DELETED infra/cert-manager.yaml HelmRepository jetstack HelmRelease · chart 1.21.x DELETED apps/web/deployment.yaml replicas: 3 DELETED apps/web/web-canary.yaml Deployment web-canary an old experiment DELETED EKS CLUSTER shop-prod · us-east-1 NAMESPACE flux-system source-controller GitRepository flux-system kustomize-controller server-side apply, then prune helm-controller reconciles HelmReleases notification-controller Receiver: GitHub webhook Alert + Provider → Slack NAMESPACE cert-manager cert-manager + CRDs: Certificate, Issuer, … NAMESPACE web · LIVE STATE Deployment web Certificate web-tls Deployment web-canary 1 replica · web:1.3-rc from web-canary.yaml DELETED

    2Quiz to check understanding

    Check yourself