Klask - Helm Deployment Guide

Installation

helm repo add klask https://charts.klask.dev
helm repo update
helm install klask klask/klask -f values.yaml

Basic Configuration (values.yaml)

Here's a minimal configuration to get started:

# Backend configuration
backend:
  replicaCount: 2
  image:
    repository: klask/backend
    tag: latest
  resources:
    requests:
      cpu: 100m
      memory: 256Mi
    limits:
      cpu: 500m
      memory: 512Mi

# Frontend configuration
frontend:
  replicaCount: 2
  image:
    repository: klask/frontend
    tag: latest
  resources:
    requests:
      cpu: 50m
      memory: 128Mi
    limits:
      cpu: 200m
      memory: 256Mi

# PostgreSQL database
postgresql:
  enabled: true
  auth:
    username: klask
    password: changeme
    database: klask

# Ingress configuration
ingress:
  enabled: true
  className: nginx
  hosts:
    - host: klask.yourdomain.com
      paths:
        - path: /
          pathType: Prefix
  tls:
    - secretName: klask-tls
      hosts:
        - klask.yourdomain.com

Key Configuration Parameters

Backend

backend.replicaCount - Number of backend pods (default: 2)
backend.resources - CPU and memory limits
backend.env - Environment variables (database URL, JWT secret, etc.)

Frontend

frontend.replicaCount - Number of frontend pods (default: 2)
frontend.env.VITE_API_URL - Backend API endpoint

Database

postgresql.enabled - Deploy PostgreSQL instance (default: true)
postgresql.auth.* - Database credentials
postgresql.persistence.size - Storage size (default: 8Gi)

Ingress

ingress.enabled - Enable external access (default: false)
ingress.className - Ingress controller (nginx, traefik, etc.)
ingress.hosts - Domain configuration
ingress.tls - TLS/SSL certificate configuration

Production Recommendations

Use external PostgreSQL for better reliability
Configure persistent volumes for data storage
Set up proper resource limits based on your repository size
Enable TLS with valid certificates
Configure JWT secret via Kubernetes secrets
Set up monitoring and logging

Advanced Configuration

For production deployments, consider:

# Use external PostgreSQL
postgresql:
  enabled: false

# External database connection
backend:
  env:
    DATABASE_URL: postgresql://user:pass@postgres.example.com/klask
    JWT_SECRET: your-secret-key-here

# Autoscaling
backend:
  autoscaling:
    enabled: true
    minReplicas: 2
    maxReplicas: 10
    targetCPUUtilizationPercentage: 70

More Resources

← Back to home