ZDDC
13ae1498e4
The dev chart's overlay-isolation layer (added in 9765fa2) was not
called out in helm/README.md or zddc-server-dev/Chart.yaml. Readers
comparing the two charts saw "same shape but tracks main" without
learning that the dev chart wraps the data PVC in OverlayFS so its
writes never mutate the underlying store.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
23 lines
757 B
YAML
23 lines
757 B
YAML
apiVersion: v2
|
|
name: zddc-server-dev
|
|
description: |
|
|
Development deployment of zddc-server. Tracks main HEAD (rebuilt on
|
|
every pod restart), runs at debug log level, has faster probe
|
|
cadence for quick feedback, and uses smaller resource limits.
|
|
Wraps the data PVC in OverlayFS — lower (PVC) mounted RO, upper an
|
|
ephemeral emptyDir — so dev-side writes never mutate the underlying
|
|
store, making it safe to point at the same data PVC as prod.
|
|
Intended for ephemeral / soak / preview environments — not for
|
|
production traffic.
|
|
type: application
|
|
version: 0.1.0
|
|
appVersion: "main"
|
|
home: https://zddc.varasys.io/
|
|
sources:
|
|
- https://codeberg.org/VARASYS/ZDDC
|
|
maintainers:
|
|
- name: VARASYS
|
|
keywords:
|
|
- zddc
|
|
- file-server
|
|
- development
|