Ghostfolio
This Argo CD deployment runs in the dedicated ghostfolio namespace. Its
PostgreSQL and Valkey services are separate Argo Applications in that same
namespace rather than shared services from default.
The upstream Ghostfolio chart currently lags the application release and its
cache dependency is Redis rather than Valkey. GitOps therefore uses the
chart's supported external-service settings to connect to the dedicated
same-namespace services, and overrides only the Ghostfolio image tag. The
release-specific image selection lives in values.yaml; remove that override
when the upstream chart's appVersion catches up.
ghostfolio-auth and the database/cache credentials are strict-scope
SealedSecrets declared in bootstrap/ghostfolio-secrets.yaml. Never put their
cleartext values in this directory.
The migration uses a logical dump/restore for the Ghostfolio database. The old
default/postgresql database is intentionally retained as a recovery copy;
do not drop it as routine cleanup. Valkey is a cache/queue dependency and is
started clean in its dedicated instance.