Skip to content

Conversation

@monotek
Copy link
Member

@monotek monotek commented Oct 8, 2025

What this PR does / why we need it

Which issue this PR fixes

(optional, in fixes #<issue number>(, fixes #<issue_number>, …) format, will close that issue when PR gets merged)

Special notes for your reviewer

  • work in progress

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

  • Chart Version bumped
  • Upgrading instructions are documented in the zammad/README.md

@monotek monotek marked this pull request as ready for review October 8, 2025 11:30
@monotek monotek force-pushed the bitnamiworkaround branch from c7d3330 to 16964bc Compare October 8, 2025 11:31
Signed-off-by: André Bauer <[email protected]>
@monotek monotek force-pushed the bitnamiworkaround branch from 16964bc to 491f64a Compare October 8, 2025 11:32
Signed-off-by: André Bauer <[email protected]>
@monotek monotek mentioned this pull request Oct 8, 2025
1 task
@mgruner
Copy link
Collaborator

mgruner commented Oct 8, 2025

Interesting idea. Do you really think this would be a sustainable solution? How would we be able to patch dependencies while avoiding major updates like for PostgreSQL in this PR?

@monotek
Copy link
Member Author

monotek commented Oct 9, 2025

You mean because you can't see the actual version in the image tag / SHA digest?
That's the reason for the version comment above, which you have to add whenever you update the image.
I retrieved the versions from the containers via CLI because I was unsure if the https://github.com/bitnami/containers repository is still the source of the Dockerfile.

Yes, that's a bit more work, but likely still easier than finding a new PostgreSQL Docker image and a fitting Helm chart we can use.

@mgruner
Copy link
Collaborator

mgruner commented Oct 9, 2025

How did you extract this info via cli?

@monotek
Copy link
Member Author

monotek commented Oct 9, 2025

"psql -V" for example.
Unfortunately, PostgreSQL only shows the major version, so i need to find a better way.
redis & memcached binaries are more explicit.

@greedybro
Copy link
Contributor

@monotek I looked a bit at the versions of postgreSQL and it seems that starting with the 10.x release, there is no patch versions anymore. You can see all versions published here

So the returning version of psql -V is accurate. You can also use SELECT version(); in a psql cli to check
image

@greedybro
Copy link
Contributor

greedybro commented Oct 23, 2025

i'm also curious about the format of latest@sha256:0eeb6604ad4258924850a38dfcd56697351086ede82e9c7668451c50569548b2

why use latest@ ? docker pull returns an invalid reference format when using it

@mgruner
Copy link
Collaborator

mgruner commented Oct 28, 2025

What about using cloudpirates https://artifacthub.io/packages/search?org=cloudpirates&sort=relevance&page=1 for any charts where no official chart exists yet? They seem to have redis, memcached and postgresql now. 🤷 Or is there any other alternative?

For now, it might be enough to simply switch redis and not touch the others.

@monotek
Copy link
Member Author

monotek commented Oct 28, 2025

It depends how much work you want to invest.
As far as i know the cloudpirates charts are no forks of the bitnami ones so there is likely no easy update path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants