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...