Debian12 for redis-cluster

[FaraSys]

Hello.
I upgrade OSup to debian12 for redis-cluster. I used base image minideb:bookworm and redis packages from Bitnami
After build images for redis cluster, I deployed redis-cluster in k8s cluster.
My development team tested and it work fine.
Ps. Sorry for my English.

[FaraSys]

Redis-cli -> info server

# Server
redis_version:7.2.1
redis_git_sha1:00000000
redis_git_dirty:0
redis_build_id:ff6a4a1b70489d10
redis_mode:cluster
os:Linux 5.15.0-76-generic x86_64
arch_bits:64
monotonic_clock:POSIX clock_gettime
multiplexing_api:epoll
atomicvar_api:c11-builtin
gcc_version:12.2.0
process_id:1
process_supervised:no
run_id:72f7d3231a423728312581630ca1029cc101f178
tcp_port:6379
server_time_usec:1695801849485544
uptime_in_seconds:8317
uptime_in_days:0
hz:10
configured_hz:10
lru_clock:1303033
executable:/redis-server
config_file:
io_threads_active:0
listener0:name=tcp,bind=0.0.0.0,bind=::,port=6379

kubectl exec -it -n redis-cluster redis-cluster-0 cat /etc/debian_version

Defaulted container "redis-cluster" out of: redis-cluster, redis-module-preload (init)
12.1

I have no name!@redis-cluster-0:/$ redis-cli -c

I have no name!@redis-cluster-0:/$ redis-cli -c              
127.0.0.1:6379> AUTH pass
OK
127.0.0.1:6379> SET mykey mykeyvalue
-> Redirected to slot [14687] located at 10.233.71.149:6379
OK
10.233.71.149:6379> GET mykey
"mykeyvalue"
10.233.71.149:6379> 

[carrodher]

Thank you for your PR. We sincerely appreciate your contribution to Bitnami. Unfortunately, we are unable to merge it at this time due to compatibility issues.

• The Bitnami Application Catalog (OpenSource) currently relies on Debian 11 as its base.
• Additionally, as part of VMware, Bitnami offers a custom container and Helm Charts catalog based on various base images, including Debian 10, 11 & 12, PhotonOS 3 & 4, Ubuntu 20.04 & 22.04, RedHat UBI 8 & 9, and custom golden images. You can explore these options through the VMware Application Catalog.

We do have plans to migrate the Bitnami Application Catalog (OpenSource) to Debian 12 in the future. However, this is a complex process that requires careful planning and adjustments to our internal testing and release pipeline. Rest assured, we will communicate the changes once we are ready to proceed.

Once again, thank you for your contribution, and we hope to work together on future projects.