How iam-veeramalla/helm-zero-to-hero works
Project type and purpose
• This is a “helm-zero-to-hero” tutorial repository aimed at teaching Helm basics.
• It includes four tutorial markdown files (01-04) explaining Helm concepts and two example microservices (“payments” and “shipping”) packaged as Helm charts under the “best-commerce” chart repository.
File structure
• Top-level:
• 01-04-*.md – sequential lesson content (what Helm is, its components, how to create & deploy charts).
• best-commerce/ – a Helm chart repo containing:
– index.yaml – the chart repository index.
– payments-0.1.0.tgz & shipping-0.1.0.tgz – packaged charts.
– payments/ and shipping/ directories – each with Chart.yaml, values.yaml, .helmignore, and a templates/ folder (deployment.yaml, service.yaml, ingress.yaml, hpa.yaml, serviceaccount.yaml, tests, _helpers.tpl).
• No application source code—only chart definitions and tutorial docs.
README
• Confirms the goal: “Learn Helm from basics.” No further architectural notes.
a. Main components
• Developer workstation (helm CLI + git)
• Chart repository (best-commerce; HTTP server hosting index.yaml + .tgz artifacts)
• Helm client/server interaction (Helm v3 is client-only but conceptualizes client → Tiller for Helm v2; for v3 show only Helm CLI → K8s API)
• Kubernetes cluster:
• API server
• payments deployment & pods, shipping deployment & pods
• Services (ClusterIP)
• Ingress controller & Ingress resources
• HorizontalPodAutoscaler for each service
b. Relationships & interactions
• Developer edits chart source (templates + values.yaml) → helm package → .tgz
• helm repo index (index.yaml) updated → chart repo server
• Developer runs helm install/upgrade pointing at chart repo URL → Helm CLI renders templates client-side, then calls Kubernetes API
• Kubernetes API creates/updates Deployments, Services, HPAs, Ingress, ServiceAccounts
• Ingress controller routes external HTTP traffic to service endpoints
c. Architectural patterns & design principles
• Template-driven, values-driven configuration (separation of concerns)
• Microservice separation: each of payments & shipping is its own chart, deployable independently
• Git-ops friendly: chart repo as source of truth
• Declarative, idempotent resource definitions
d. Key technologies & frameworks
• Helm v3, Kubernetes API, Ingress controller (e.g., nginx), HorizontalPodAutoscaler (metrics server)
• Chart schema & templating engine (Go templates)
• HTTP-based chart repository (could be GitHub Pages, S3, etc.)