~/ nmadiraju.com Amazon EKS · Kustomize
arrow_back Back to nmadiraju
Visual Walkthrough · Kubernetes fundamentals

How Kustomize Works on Amazon EKS

Follow one app, web, from copied YAML to a base and a prod overlay, through three gotchas, then check yourself with 8 questions.

1Visual Walkthrough

A Kustomize base and overlays in Git, built by kubectl or Argo CD and applied to an EKS namespace Left, a Git repo with web's YAML: a base with kustomization.yaml and overlays for dev and prod. Middle, kubectl or Argo CD building the overlay into rendered YAML, and a vendor's Helm chart. Right, the EKS cluster: the API server, Deployment web, its Pods, ConfigMaps and Service web in namespace shop. GIT REPO · apps/web dev/ · 3 files deployment.yaml service.yaml configmap.yaml image: web:1.5 prod/ · 3 files deployment.yaml service.yaml configmap.yaml image: web:1.4 (missed) base/ · kustomization.yaml overlays/dev resources: - ../../base namespace: shop-dev overlays/prod resources: - ../../base namespace: shop patch: replicas → 5 images: web → tag 1.5 You · kubectl kubectl apply -k · kubectl kustomize Argo CD · Application web-prod in-cluster · path: overlays/prod Rendered YAML A vendor's Helm chart kubectl kustomize --enable-helm needs the helm binary; apply -k can't EKS CLUSTER · NAMESPACE shop API server EKS control plane stores the objects Deployment web Pods ConfigMaps Service web selector: app=web · port 80 → 8080

    2Quiz to check understanding

    Check yourself