Update Bitnami chart dependencies to fix ImagePullBackOff errors

[Copilot]

Bitnami migrated to "Secure Images" initiative on August 28, 2025, deprecating specific version tags (e.g., 11.4.5-debian-12-r9) from their public registry. Charts using old dependency versions fail to pull images.

Changes

• MariaDB chart: 20.4.2 → 23.2.2
• PostgreSQL chart: 16.6.0 → 18.1.4
• Updated Chart.lock and regenerated README.md

New versions use latest tags (bitnami/mariadb:latest, bitnami/postgresql:latest) which are actively maintained in the public registry per Bitnami's Secure Images program.

Before

dependencies:
- name: mariadb
  repository: oci://registry-1.docker.io/bitnamicharts
  version: 20.4.2  # References docker.io/bitnami/mariadb:11.4.5-debian-12-r9 (not found)

After

dependencies:
- name: mariadb
  repository: oci://registry-1.docker.io/bitnamicharts
  version: 23.2.2  # References registry-1.docker.io/bitnami/mariadb:latest

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• charts.bitnami.com
  • Triggering command: helm repo add bitnami REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>mariadb problem.</issue_title>
<issue_description>Hello there,

I can not start the chart with mariadb backend. I get these:

2025-11-03 09:12:52 | mariadb-0 | Pod | Normal | Back-off pulling image "docker.io/bitnami/mariadb:11.4.5-debian-12-r9"
2025-11-03 09:12:52 | mariadb-0 | Pod | Warning | Error: ImagePullBackOff
2025-11-03 08:25:47 | mariadb-0 | Pod | Warning | Failed to pull image "docker.io/bitnami/mariadb:11.4.5-debian-12-r9": rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/bitnami/mariadb:11.4.5-debian-12-r9": failed to resolve reference "docker.io/bitnami/mariadb:11.4.5-debian-12-r9": docker.io/bitnami/mariadb:11.4.5-debian-12-r9: not found
2025-11-03 08:25:47 | mariadb-0 | Pod | Warning | Error: ErrImagePull
2025-11-03 08:25:46 | mariadb-0 | Pod | Normal | Pulling image "docker.io/bitnami/mariadb:11.4.5-debian-12-r9"
2025-11-03 08:22:37 | mariadb-0 | Pod | Normal | Successfully assigned semaphore/mariadb-0 to hun25-35v.hft.rosenberger.local
2025-11-03 08:22:37 | mariadb | StatefulSet | Normal | create Pod mariadb-0 in StatefulSet mariadb successful

i think it is the problem.....

⚠️ Important Notice: Upcoming changes to the Bitnami Catalog
Beginning August 28th, 2025, Bitnami will evolve its public catalog to offer a curated set of hardened, security-focused images under the new Bitnami Secure Images initiative⁠. As part of this transition:

Granting community users access for the first time to security-optimized versions of popular container images.
Bitnami will begin deprecating support for non-hardened, Debian-based software images in its free tier and will gradually remove non-latest tags from the public catalog. As a result, community users will have access to a reduced number of hardened images. These images are published only under the “latest” tag and are intended for development purposes
Starting August 28th, over two weeks, all existing container images, including older or versioned tags (e.g., 2.50.0, 10.6), will be migrated from the public catalog (docker.io/bitnami) to the “Bitnami Legacy” repository (docker.io/bitnamilegacy), where they will no longer receive updates.
For production workloads and long-term support, users are encouraged to adopt Bitnami Secure Images, which include hardened containers, smaller attack surfaces, CVE transparency (via VEX/KEV), SBOMs, and enterprise support.
These changes aim to improve the security posture of all Bitnami users by promoting best practices for software supply chain integrity and up-to-date deployments. For more details, visit the Bitnami Secure Images announcement⁠.

edit:

now i rewrite bitnami to bitnamilegacy on values.yaml, but it is only temp solution...</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes mariadb problem. #12

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.