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

How Helm Works on Amazon EKS

Follow one app, web, from copied YAML to a Helm chart in prod, through upgrades, a conflict and a rollback, then check yourself with 8 questions.

1Visual Walkthrough

A Helm chart on your laptop, stored in Amazon ECR, installed into an EKS namespace as a release with revisions Left, your laptop: the helm CLI, the chart web with its templates and default values, a values file per environment and the rendered manifests. Middle, Amazon ECR holding the chart, and a teammate using kubectl. Right, the EKS cluster: the API server, the release's revision Secrets, and the Deployment, ConfigMap, Service and Ingress for web in namespace shop. YOUR LAPTOP You · helm CLI Helm 4 · kubectl Chart web 0.3.0 templates/ deployment.yaml service.yaml configmap.yaml ingress.yaml values.yaml (defaults) replicaCount: 2 · tag: 1.4 dev/ · 4 files deployment.yaml service.yaml configmap.yaml ingress.yaml image: web:1.5 prod/ · 4 files deployment.yaml service.yaml configmap.yaml ingress.yaml image: web:1.4 (missed) values-dev.yaml replicaCount: 1 host: dev.example.com values-prod.yaml host: shop.example.com Rendered manifests (4 objects) Amazon ECR images: web:1.4, 1.5 Teammate kubectl edit deployment web EKS CLUSTER · NAMESPACE shop API server EKS control plane checks your access Release web: Secrets sh.helm.release.v1.web.vN Deployment web ConfigMap web LOG_LEVEL: info DB_HOST: db.shop Service web port 80 → 8080 Ingress web shop.example.com

    2Quiz to check understanding

    Check yourself