Migrating Bitnami Images and Long-term Maintenance Strategies

[kingsword09]

Due to Bitnami’s upcoming restriction on free access to most images after August 28, 2025 #6434, i migrated the CI images for etcd, memcached, redis, and redis-cluster to new sources in PR #6435 (including gcr.io, bitnamisecure, and bitnamilegacy). During this migration, several issues were encountered:

• The official etcd image does not support the ‎ETCD_ROOT_PASSWORD environment variable, so we temporarily switched to ‎bitnamilegacy/etcd.
• The ‎bitnamisecure/memcached image throws a ‎saslpasswd2: command not found error when authentication is enabled. This issue has been reported to Bitnami, and we are currently using ‎bitnamilegacy/memcached as a workaround.
• Since bitnamilegacy images will not receive future updates, relying on them poses long-term maintenance and security risks. At present, there are few actively maintained alternatives for etcd and memcached.

I’d like to invite the community to discuss and share suggestions on the following points:

1. Are there any recommended alternatives for etcd or memcached images that are compatible and actively maintained?
2. What are the best temporary or long-term strategies for dealing with legacy image dependencies?
3. Any experiences or best practices for CI/CD image maintenance are welcome.