Files
feedc0de 3795736e5e
Validate, publish and promote loops chart / publish (push) Successful in 2s
Validate, publish and promote loops chart / validate (push) Successful in 1s
Package loops Kubernetes deployment
2026-10-22 17:39:25 +02:00

21 lines
1.3 KiB
Markdown

# loops Helm chart
This chart owns the loops web and worker topology, its MySQL and Valkey
services, persistent claims, probes, and optional Traefik route. It expects
existing Kubernetes Secrets named by `runtimeSecret`, `mysql.authSecret`,
`valkey.authSecret`, and (when bucket bootstrap is enabled)
`s3BucketJob.secretName`. Never put their values in a public values file.
For this homelab, [cluster-specific values](https://code.brunner.ninja/feedc0de/homelab-gitops/src/branch/main/apps/loops/values.yaml)
select the existing PVC names, storage classes, domain and Secret names. A fresh
installation may choose different storage; migrating a live installation must
preserve its PVC UIDs and database contents.
```sh
helm repo add brunner.ninja https://brunner.ninja/charts
helm repo update brunner.ninja
helm upgrade --install loops brunner.ninja/loops --namespace loops --create-namespace --wait --timeout 20m
```
The deployed image is built from Loops source commit f614b34f. The chart's frontend, backend and Following-feed overlays are tied to that exact image; review and rebase them before changing `appVersion` or `image.tag`. The upstream project does not issue SemVer releases for this commit, so Git tag `f614b34f` maps reversibly to chart version `0.0.0-f614b34f`; chart-only commits append their Git-describe count and hash.