feat: add Helm chart with PostgreSQL, MariaDB, and Redis support

[Copilot]

Kutt had no Kubernetes deployment story. This adds a production-ready Helm chart under helm/kutt/ following standard best practices, with optional Bitnami sub-charts for PostgreSQL, MariaDB, and Redis.

Chart structure

• Chart.yaml — appVersion: 3.2.3, conditional Bitnami dependencies (postgresql >=16<17, mariadb >=20<21, redis >=20<21)
• values.yaml — Full coverage of all Kutt env vars: JWT, DB, Redis, SMTP, OIDC, feature flags, link settings
• templates/
  • configmap.yaml — Non-sensitive config; auto-derives DB_CLIENT, DB_HOST, DB_PORT from whichever sub-chart is enabled
  • secret.yaml — JWT, DB password, Redis password, SMTP password, OIDC client secret; supports existingSecret references for all
  • deployment.yaml — Pulls env from ConfigMap + per-key secretKeyRef for sensitive values
  • pvc.yaml — SQLite persistence (skipped when PostgreSQL or MariaDB is enabled)
  • Standard: service, ingress, hpa, serviceaccount, _helpers.tpl, NOTES.txt
• ci/ — Separate values files for SQLite, PostgreSQL, and MariaDB CI test scenarios

Database modes

# PostgreSQL + Redis
postgresql:
  enabled: true
  auth:
    password: changeme
redis:
  enabled: true

# MariaDB + Redis
mariadb:
  enabled: true
  auth:
    password: changeme
    rootPassword: changeme
redis:
  enabled: true

# Default: SQLite with PVC (no sub-charts needed)

DB_CLIENT, DB_HOST, and DB_PORT in the ConfigMap are templated via _helpers.tpl and resolve automatically based on which sub-chart is active — no manual wiring required.

Usage

helm repo add bitnami https://charts.bitnami.com/bitnami
helm dependency update helm/kutt
helm install my-kutt helm/kutt \
  --set kutt.auth.jwtSecret=$(openssl rand -hex 32) \
  --set kutt.defaultDomain=kutt.example.com \
  --set postgresql.enabled=true \
  --set postgresql.auth.****** \
  --set redis.enabled=true

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• charts.bitnami.com
  • Triggering command: /usr/local/bin/helm helm repo add bitnami REDACTED (dns block)
  • Triggering command: /usr/local/bin/helm helm template myrelease helm/kutt/ --set kutt.auth.jwtSecret=mysecret --skip-crds --dependency-update (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>feat: add helm chart</issue_title>
<issue_description>need to add an helm chart for kutt
we will use standard best practices for helm chart and dependencies to handle postgresql and redis (i'm interested in mariadb variant)</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes feat: add helm chart #2

---

⌨️ Start Copilot coding agent tasks without leaving your editor — available in VS Code, Visual Studio, JetBrains IDEs and Eclipse.