vscode-extensions/archify-vscode-ext-sync
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Chart: postgresql.existingClaim for a database volume made outside the chart

Browse Source
This commit is contained in:
Oleg Lukasonok committed 2026-11-06 21:23:49 +02:00
1 parent 99778d7489
commit d8d46266dc
4 files changed
+12 -2
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

README.md
+1 -1
View File
@@ -57,7 +57,7 @@ helm install sync charts/archify-sync -n archify-sync --create-namespace \
--set database.existingSecret=archify-sync-db # a Secret with the URL under "url"
```
`postgresql.enabled=true` adds a single PostgreSQL to the release, for trying out. Behind ingress-nginx, raise `proxy-read-timeout` and `proxy-send-timeout` (see `values.yaml`): edits travel over a WebSocket that stays open.
`postgresql.enabled=true` adds a single PostgreSQL to the release, for trying out. `postgresql.existingClaim` puts its data on a claim made outside the chart; PostgreSQL runs as uid 70 and needs that directory owned by 70, mode 0700, so an NFS share must not map every user to root. Behind ingress-nginx, raise `proxy-read-timeout` and `proxy-send-timeout` (see `values.yaml`): edits travel over a WebSocket that stays open.
On a local cluster (OrbStack, kind, k3d) with the image from `docker build -t archify-sync:local .`: