Skip to content

docs(readme): keep a pre-pin release on its own Postgres and Redis images - #29

Open
leandrolerena wants to merge 2 commits into
mainfrom
fix/30-helm
Open

leandrolerena wants to merge 2 commits into
mainfrom
fix/30-helm

Conversation

@leandrolerena

Copy link
Copy Markdown
Member

What was wrong

#28 pinned the Bitnami images in charts/neops/values.yaml to bitnamilegacy/postgresql:17.6.0-debian-12-r4 and bitnamilegacy/redis:8.2.1-debian-12-r0. Before that, the base values set no image: for either subchart, so a release installed from them ran the vendored charts' default (charts/neops/charts/postgresql-18.8.17.tgz and redis-28.0.15.tgz both default to tag: latest). Today that is bitnami/postgresql:latest = 18.6.0 and bitnami/redis:latest = 8.10.3.

Running helm upgrade on such a release with the new pins starts Postgres 17 on an 18 data directory, which Postgres refuses to open. It also starts Redis 8.2 on an RDB file a newer Redis wrote, which it may refuse. bitnamilegacy publishes no Postgres 18 and no Redis newer than 8.2.1, so there is no pin to move to. KIND releases (values-kind.yaml) had the pins all along and are not affected.

What changes

Docs and comments only:

  • README.md: a new section, "Upgrading a release installed before the Bitnami pins". It explains the risk, gives a kubectl command that reads the image and imageID the Postgres and Redis pods run, and shows how to keep exactly that image by pinning its digest in the environment values file. It also says that moving such a release onto Postgres 17 needs a dump and restore, which the chart does not do.
  • charts/neops/values.yaml: comments on the postgresql.image and redis.image pins that point to that section.

How it was verified

This repo's CI only checks the PR label, so everything below was run by hand. Nothing was deployed and no cluster was touched.

  • helm dependency build and helm lint pass for both values.yaml and values-kind.yaml.
  • helm template output before and after this change is identical for both values files, apart from randomly generated secrets.
  • The README's digest override renders as registry-1.docker.io/bitnami/postgresql@sha256:... and registry-1.docker.io/bitnami/redis@sha256:...: the subchart's common.images.image drops the tag when a digest is set. global.security.allowInsecureImages: true (charts/neops/values.yaml:20) keeps Bitnami's modified-image check from blocking it.
  • docker manifest inspect confirms the four pinned bitnamilegacy images exist. The bitnami/*:latest image labels confirm 18.6.0 and 8.10.3.

Not verified

  • The kubectl ... -o jsonpath command was not run against a cluster.
  • No helm upgrade from a release that ran latest was attempted, with or without the digest override.
  • Not checked: whether an old digest of bitnami/*:latest can still be pulled. Bitnami's free repositories now keep only latest, so an operator who relies on that digest may want to mirror it into their own registry.
  • The section hardcodes namespace neops and the neops- pod prefix, like the rest of README.md. The last paragraph explains the <release> form.

For the maintainer

The release notes for #28 do not warn about this downgrade. Relabel that PR pr-breaking-change, or relabel this one, if they should.

This repo is not part of docs.neops.io, so this change does not reach the public docs site.

…ages

Releases installed from the base values before d725f56 ran the charts'
default bitnami/postgresql:latest (18.6.0 today) and bitnami/redis:latest
(8.10.3). Upgrading them onto the bitnamilegacy pins starts Postgres 17 on
an 18 data directory, which Postgres refuses, and Redis 8.2 on a newer
RDB file. bitnamilegacy has no Postgres 18, so document how to find the
running image and pin its digest in the environment values file, and point
the postgresql and redis pins in values.yaml at that section.

The rendered output of values.yaml and values-kind.yaml is unchanged.
@leandrolerena leandrolerena added the pr-other PR does something not covered by other labels label Nov 9, 2026
@leandrolerena leandrolerena self-assigned this Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-other PR does something not covered by other labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant