Helm Charts Setup for Web Application Deployment

Setting Up Helm Charts for Web Application Deployment

You've deployed a Kubernetes cluster, but YAML manifests for each microservice have ballooned into dozens of files. Every environment has its own set of parameters, and during deployment it's easy to make a mistake with replicas or image tags. Helm — the package manager for Kubernetes — solves this with parameterized templates and values files.Source: Helm Official Site We set up Helm Charts for your projects end-to-end: from structure design to CI/CD integration. Over 5 years we've configured Helm for more than 50 projects — from small startups to clusters with hundreds of pods. Our experience helps avoid typical mistakes like hardcoding image tags or missing readiness probes. Using Helm cuts deployment time for a new service from 2 hours to 15 minutes (a 75% reduction), with built-in versioning and automatic rollback on failure. This article explains how we approach Helm Chart setup and which problems it solves.

Problems We Solve

• Manifest duplication — for staging and prod you have to copy dozens of files and manually tweak parameters. Helm with values files eliminates duplication: one template, different values.
• No versioning — after deployment it's hard to know which version is running. Helm stores release history with labels and enables rollback.
• Complex dependency configuration — Redis, PostgreSQL, sidecar containers must be described manually. Helm dependencies pull ready charts from repositories like Bitnami.

How Helm Charts Simplify Deployment

Consider an example. For a client with 5 microservices we designed a common Helm chart with overlays per environment. The main chart includes templates for Deployment, Service, Ingress, HPA, ConfigMap, and Secret. Repeated labels and annotations are extracted into _helpers.tpl. Values files (values.dev.yaml, values.prod.yaml) contain only the varying parameters: replicas, resources, image tags. Result: deploying a new service takes 15 minutes instead of 2 hours.

Typical chart structure:

myapp/
├── Chart.yaml
├── values.yaml
├── values.prod.yaml
├── values.staging.yaml
└── templates/
    ├── deployment.yaml
    ├── service.yaml
    ├── ingress.yaml
    ├── hpa.yaml
    ├── configmap.yaml
    ├── secret.yaml
    └── _helpers.tpl

Example values.yaml:

replicaCount: 2
image:
  repository: myapp
  tag: "latest"
  pullPolicy: IfNotPresent
service:
  type: ClusterIP
  port: 80
  targetPort: 8080
resources:
  requests:
    cpu: 100m
    memory: 256Mi
  limits:
    cpu: 500m
    memory: 512Mi
autoscaling:
  enabled: false
  minReplicas: 2
  maxReplicas: 10
  targetCPUUtilizationPercentage: 70

deployment.yaml template uses Go templating:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: {{ include "myapp.fullname" . }}
  labels: {{ include "myapp.labels" . | nindent 4 }}
spec:
  replicas: {{ .Values.replicaCount }}
  selector:
    matchLabels: {{ include "myapp.selectorLabels" . | nindent 6 }}
  template:
    metadata:
      labels: {{ include "myapp.selectorLabels" . | nindent 8 }}
      annotations:
        checksum/config: {{ include (print $.Template.BasePath "/configmap.yaml") . | sha256sum }}
    spec:
      containers:
        - name: {{ .Chart.Name }}
          image: "{{ .Values.image.repository }}:{{ .Values.image.tag | default .Chart.AppVersion }}"
          imagePullPolicy: {{ .Values.image.pullPolicy }}
          ports:
            - containerPort: {{ .Values.service.targetPort }}
          envFrom:
            - configMapRef:
                name: {{ include "myapp.fullname" . }}
            - secretRef:
                name: {{ include "myapp.fullname" . }}
          resources: {{ toYaml .Values.resources | nindent 12 }}

Why Helm Charts Are Faster Than Plain Manifests

Helm Charts allow deploying new services 4x faster compared to plain YAML, and error rates drop 3–5x. Our clients save an average of $2,000 per month by eliminating manual YAML errors. Comparison of key metrics:

Common Mistakes in Helm Setup

• Hardcoded image tags — always use image.tag variables and override them in CI.
• Missing probes — configure readiness and liveness; otherwise K8s doesn't know if the service is alive.
• Secrets in values — always use secrets in YAML and pass via --set secrets.* or external stores.

Why Configure Helm Through Our Service

We've implemented Helm in 50+ projects — from startups to enterprise clusters with hundreds of pods. We guarantee compatibility with your cluster and Kubernetes version. We use up-to-date approaches: config checksums for change tracking, atomic releases for automatic rollback, and integration with ArgoCD for GitOps workflows. Our process includes YAML templating best practices and release management strategies.

Process

1. Analysis — study the architecture, environments, CI/CD. Identify required components: services, databases, ingress controllers.
2. Design — develop chart structure, values files, extract common helpers.
3. Development — write templates, add dependencies (redis, postgres), configure HPA and probes.
4. Testing — run helm install --dry-run --debug, verify all manifests.
5. Deployment — install with helm upgrade --install --atomic, set up CI/CD (GitHub Actions, GitLab CI).
6. Documentation — deliver chart description and command cheat sheet, train the team.

Estimated Timelines & Pricing

Pricing includes documentation and team training. Start saving $2,000/month by eliminating manual YAML errors.

What's Included

• Helm chart with templates for Deployment, Service, Ingress, HPA, ConfigMap, Secret.
• Values files for environments (dev, staging, prod).
• CI/CD integration (GitHub Actions, GitLab CI).
• Documentation on chart structure and deployment commands.
• Team training (2 hours).
• 2 weeks of post-launch support.

If you want to speed up deployments and eliminate YAML drudgery, contact us for a consultation. Order Helm Charts setup — we'll find the optimal structure for your project.

We regularly encounter a situation: "The site is not opening" at 3 a.m. — and it turns out that the VPS disk is full because nginx logs haven't been rotated for six months. Or the server went down under load on the day of an advertising campaign launch because the shared hosting had a limit of 50 concurrent connections. Setting up hosting and deployment is not about "where it's cheaper" but about what happens when something goes wrong. Our team helps avoid such incidents by designing infrastructure that accounts for real load patterns.

When to choose Vercel and Netlify?

Vercel is built for Next.js — deploy in one push, preview deployments for every PR, automatic CDN, Edge Functions, ISR without configuration. For frontend projects and JAMstack, it's the optimal choice: no operational overhead, time-to-deploy measured in minutes.

Real limitations: Vercel Serverless Functions run in us-east-1 by default (latency for Europe +80–100ms), Function timeout 300 seconds on Pro, Bandwidth 1TB/month on Pro. For heavy backend, you need workers or a separate server.

Netlify is closer to static sites and Edge Functions based on Deno Deploy. Build minutes are the main limitation on the free tier.

Why is Docker the foundation of predictable deployment?

"It works on my machine" — classic. Docker solves this through environment containerization. But a bad Dockerfile creates new problems.

A typical mistake: copying everything into the image without .dockerignore, resulting in an 800MB image instead of 80MB. node_modules inside the image weighs as much. Correct approach: multi-stage build.

FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
RUN npm run build

FROM node:20-alpine AS runner
WORKDIR /app
COPY --from=builder /app/.next ./.next
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/package.json ./package.json
EXPOSE 3000
CMD ["npm", "start"]

Final image: 180MB instead of 1.2GB. CI build time is reduced due to layer caching — if package.json hasn't changed, the layer with npm ci is taken from cache.

Docker Compose for local development and simple production scenarios: application + PostgreSQL + Redis in one configuration. For production on a single server, it's a perfectly viable option if there's no requirement for horizontal scaling.

More about containerization — Wikipedia: Docker.

How to set up Nginx as a reverse proxy?

Nginx in front of the application is standard for VPS and dedicated servers. Main functions: SSL termination, gzip, static files, rate limiting, upstream load balancing.

A configuration often done incorrectly: worker_processes auto — number of processes equals CPU count. worker_connections 1024 — that's 1024 per worker process. With 4 CPUs and 1024 connections = 4096 concurrent connections. For a high-traffic site, you need worker_connections 4096 and set keepalive_timeout 65.

For static assets with hash in the filename:

location ~* \.(js|css|woff2|png|webp)$ {
    expires 1y;
    add_header Cache-Control "public, immutable";
}

immutable tells the browser: don't revalidate this file even on hard refresh. This only works correctly with content-hashed filenames (which Vite/webpack do by default). Documentation — Wikipedia: Nginx.

AWS: flexibility and complexity

EC2 + Auto Scaling Group — classic for horizontal scaling. AMI with pre-installed application, Launch Template, ASG with min/desired/max instances, Application Load Balancer. When CPU > 70% for 3 minutes — scale out, when CPU < 30% for 15 minutes — scale in. Health check via ALB removes unhealthy instances from rotation.

ECS Fargate — containers without managing EC2. Deploy a Docker image, specify CPU/memory (512 CPU units = 0.5 vCPU, from 512MB memory), Fargate launches it. More expensive than Lambda, but no cold start and no timeout limitations. Suitable for long-running processes, WebSocket servers, heavy workers.

RDS for PostgreSQL with Multi-AZ: automatic failover in 1–2 minutes when primary fails. Read Replicas for scaling reads. RDS Proxy for connection pooling — Lambda functions cannot hold long-term connections, the proxy buffers this.

Kubernetes: when it is justified

K8s adds significant operational complexity. Justified when: multiple teams deploy independent services, fine-grained resource allocation per service is needed, canary deployments and blue/green without downtime are required.

AWS EKS, GKE, or managed k8s from Hetzner (cheaper). Helm charts for standard services. Horizontal Pod Autoscaler based on CPU and custom metrics (RPS via Prometheus).

For most startups and medium-sized projects, Kubernetes is overkill. ECS or Fly.io provide 80% of the capabilities with 20% of the operational complexity.

Monitoring and alerting

A server without monitoring is waiting for an incident. Minimal stack: Prometheus + Grafana (or Grafana Cloud for managed), alerting on disk > 80%, memory > 85%, CPU > 90% over 5 minutes, error rate > 1%. Uptime via Better Uptime or Upptime (self-hosted).

Logs: Loki + Grafana or CloudWatch Logs Insights. Structured JSON logs (winston, pino) are mandatory — otherwise, log searching becomes a pain.

What is included in hosting setup

• Audit of current infrastructure and load profiling
• Selection of target architecture (VPS, AWS, serverless, Kubernetes)
• Setting up CI/CD pipeline (GitHub Actions, GitLab CI) with automatic deployment
• IaC via Terraform or Pulumi (infrastructure as code)
• Configuration of Nginx, SSL certificates, HTTP/2, brotli
• Monitoring and alerting (Prometheus + Grafana, PagerDuty)
• Documentation of runbooks and team training

Additionally, contact us if you need migration from current hosting or integration with external services.

Work process

1. Audit of current infrastructure (2–5 days)
2. Selection of target architecture with load and budget justification (1–3 days)
3. Setting up CI/CD pipeline (GitHub Actions, GitLab CI) (2–5 days)
4. IaC via Terraform or Pulumi (3–10 days)
5. Setting up monitoring and alerting (2–5 days)
6. Documentation of runbooks and team training (1–3 days)

Our experience — 7 years on the market, over 50 projects, guarantee of operability after deployment.

Timeline

• Basic deployment on VPS with Docker + Nginx + CI/CD: 1–2 weeks.
• Setting up AWS infrastructure with Auto Scaling, RDS, CDN: 3–6 weeks.
• Migration to EKS from scratch: 6–12 weeks.
• Setting up Vercel/Netlify for JAMstack: 3–5 days.

The cost is calculated individually depending on complexity and scope of work. Get a consultation — we'll evaluate your architecture in one day.