Removing legacy chart versions from the Helm index
If you've been getting helm repo update warnings — or if you watch our
ArtifactHub feed — you may have noticed errors about a missing Bitnami
Postgres image:
error scanning image docker.io/bitnami/postgresql:14.5.0-debian-11-r35:
image not found (package platzio:0.6.2)
We've removed the entries that triggered it.
What happened
Platz chart versions up to and including 0.6.2 declared a dependency on
the Bitnami PostgreSQL subchart, which
in turn pulled docker.io/bitnami/postgresql:14.5.0-debian-11-r35. In late
2025 Bitnami moved their historical image tags to a separate
bitnamilegacy namespace and deleted them from docker.io/bitnami/*. The
Helm chart still references the old path, so scanners (and anyone trying
a fresh install of an old version) get a 404.
The dependency itself was removed in v0.6.3. The reasoning is in the
v0.6.8 release notes and on the
Database page: operators get full control
over the database, and Platz doesn't ship with a specific database chart.
What changed
We removed entries <= 0.6.2 from the Helm repository
index. The repository
now serves 0.6.3 through 0.6.8. That's enough history to roll back
across the post-Bitnami removal; everything older was tied to the broken
dependency anyway.
The release tarballs themselves are untouched — they still live on GitHub Releases. If you've pinned a specific older version by URL in your own automation, it will continue to resolve.
What you should do
- If you're on
0.6.3or later: nothing. You won't see any change. - If you're still on
0.6.2or earlier: plan an upgrade to the latest0.6.x. Provision Postgres yourself (RDS, Cloud SQL, self-hosted — see the Database page), populate thepostgres-credssecret, and bump the chart. The schema migration runs automatically on API pod startup. - If you depended on the bundled Bitnami subchart in production: same as above. The bundled subchart was never intended for serious production use, and it's now structurally broken; migrating off it is the path forward.