Files
feedc0de fdd46cbb16
Validate, publish and promote Quay chart / chart (push) Successful in 44s
Document Quay database modes and namespace default
2026-10-24 19:03:07 +02:00

32 lines
1.6 KiB
Markdown

# Project Quay Helm chart
This repository maintains a [portable Quay chart](chart/README.md) with the
official Quay image, registry and mirror Deployments, Service, Ingress, probes,
and optional PostgreSQL and Valkey subcharts, plus a CloudNativePG mode. It is
published to the public
[brunner.ninja Helm repository](https://brunner.ninja/charts):
```sh
helm repo add brunner.ninja https://brunner.ninja/charts
helm repo update brunner.ninja
```
For a cluster installation, first provision an S3-compatible bucket and a
private Quay `config.yaml` Secret as described in the chart documentation.
Set the chart values for your database, cache, hostname, and storage, then run
`QUAY_VALUES_FILE=values.yaml ./install.sh`. The script performs a waiting Helm
upgrade. The chart does not create or delete S3 buckets or their contents.
The [homelab Quay Argo CD application](https://code.brunner.ninja/feedc0de/homelab-gitops/src/branch/main/apps/quay)
holds only this cluster's values and the Rook object user. On this cluster,
Argo CD is the normal deployment writer; do not run `install.sh` against it.
The old direct-deploy workflow, kubeconfig, and duplicate manifests were
retired after adoption. This cluster now runs Quay in its own namespace with
CloudNativePG and a dedicated Valkey. PostgreSQL and Ceph data were preserved;
the old database PVC is retained for rollback.
Chart releases use Quay's application-version Git tag as the base and append
the commit count and hash for chart-only changes. Main-branch CI tests,
publishes, and promotes the exact chart version to the homelab GitOps repo.
Run `./test.sh` locally to lint and render the chart.