Re: [PR] chore(ci): migrate etcd, memcached, redis, and redis-cluster images to new sources [opendal]

["kingsword09 (via GitHub)" <gi...@apache.org>]

kingsword09 commented on PR #6435:
URL: https://github.com/apache/opendal/pull/6435#issuecomment-3188386665

   | **Old Image** | **New Image** | **Migration Notes** |
   | :--- | :--- | :--- |
   | `bitnami/memcached` | `bitnamisecure/memcached` | `bitnami` to `bitnamisecure` |
   | `bitnami/etcd:latest` | `gcr.io/etcd-development/etcd:v3.6.4` | Official image |
   | `docker.io/bitnami/redis:7.0` | `docker.io/bitnamilegacy/redis:7.4.3-debian-12-r0` | `bitnami` to `bitnamilegacy` |
   | `docker.io/bitnami/redis-cluster:7.0` | `docker.io/bitnamilegacy/redis-cluster:7.4.3-debian-12-r0` | `bitnami` to `bitnamilegacy` |
   
   ---
   
   @Xuanwo  I’m not sure how best to resolve:
   - etcd TLS migration issue:
   The official etcd image does not support the ‎`ETCD_ROOT_PASSWORD` environment variable, so we are using ‎`docker.io/bitnamilegacy/etcd:3.6.4-debian-12-r0` instead.
   - Memcached authentication issue:
   When enabling authentication with the new memcached image, the error ‎`saslpasswd2: command not found` occurs, so we switched to ‎`docker.io/bitnamilegacy/memcached:1.6.39-debian-12-r0`.
   - Legacy image maintenance:
   Images from ‎`bitnamilegacy` will not receive future updates, which may affect long-term maintenance and security, since there seem to be very few actively maintained alternatives available for etcd and memcached..
   
   I’m not sure how to address these problems and would appreciate your suggestions or guidance on possible solutions. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@opendal.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org