fix(perf): use bitnamilegacy images for Postgres and Redis
Some checks are pending
Unit Tests: Proxy DB Operations / proxy-db (auth-checks, tests/proxy_unit_tests/test_auth_checks.py tests/proxy_unit_tests/test_user_api_key_auth.py, 20, 8) (push) Waiting to run
Unit Tests: Proxy DB Operations / proxy-db (key-generation, tests/proxy_unit_tests/test_key_generate_prisma.py, 30, 0) (push) Waiting to run
Unit Tests: Proxy DB Operations / proxy-db (remaining, tests/proxy_unit_tests --ignore=tests/proxy_unit_tests/test_key_generate_prisma.py --ignore=tests/proxy_unit_tests/test_auth_checks.py --ignore=tests/proxy_unit_tests/test_user_api_key_auth.py, 30, 8) (push) Waiting to run
Unit Tests: Security / security (push) Waiting to run

docker.io/bitnami/* tags bundled with the subcharts often 404 after Bitnami
catalog changes; pin to active bitnamilegacy tags on Docker Hub.

Made-with: Cursor
This commit is contained in:
harish-berri 2026-04-22 20:01:15 +00:00
parent d39ea97128
commit e64526a4bd

View file

@ -68,6 +68,12 @@ db:
# Without this, claims stay Pending with an empty STORAGECLASS. If you already have Pending PVCs,
# delete them after syncing so StatefulSets recreate claims (wiping local DB/Redis data).
postgresql:
# docker.io/bitnami/postgresql tags from the subchart (e.g. 16.2.0-debian-12-r6) are often removed;
# use Bitnami Legacy Catalog: https://hub.docker.com/r/bitnamilegacy/postgresql/tags
image:
registry: docker.io
repository: bitnamilegacy/postgresql
tag: 16.6.0-debian-12-r2
primary:
persistence:
storageClass: gp2
@ -75,6 +81,12 @@ postgresql:
redis:
enabled: true
architecture: standalone
# Same as Postgres: chart default docker.io/bitnami/redis tags may 404; legacy catalog:
# https://hub.docker.com/r/bitnamilegacy/redis/tags
image:
registry: docker.io
repository: bitnamilegacy/redis
tag: 7.2.5-debian-12-r6
master:
persistence:
storageClass: gp2