Hi KubeSphere team,

I was reviewing the test Helm charts and noticed that src/test/radondb-postgresql/values.yaml relies on the radondb/postgresql-repmgr Docker image.

The Problem
The radondb namespace contains legacy artifacts that are no longer actively maintained. Using this unmaintained repository for a core database component means the image no longer receives critical updates, including CVE security patches.

Additionally, the upstream Bitnami images (which the RadonDB architecture is based on) have recently been placed behind a paywall with strict rate limits. If KubeSphere users attempt to fall back to Bitnami to get a newer version, they will encounter pull access denied errors. Deploying unpatched databases or facing pull limits introduces a significant vulnerability and stability risk for enterprise users relying on KubeSphere's charts.

Proposed Solution
I strongly suggest switching the repository to soldevelo/postgresql-repmgr.
This image is a free, actively maintained, and fully open-source drop-in replacement.

Crucially:

• It ensures the PostgreSQL HA stack deployed by KubeSphere users is running on a secure, actively patched foundation.
• It preserves the exact same Bitnami-style directory structure, environment variables, and repmgr replication logic that the RadonDB chart expects.
• Your existing Helm chart templates and values.yaml will continue to work immediately without requiring structural refactoring.

(Note: SolDevelo maintains a growing library of open-source, Bitnami-compatible images specifically to help the OSS community move away from deprecated, unmaintained, or paywalled artifacts. You can find the source code here: https://github.com/SolDevelo/containers)