What bitnami/charts shipped
Generated by FoxPlug from public activity — not affiliated with Bitnami.
Week of September 14, 2026
What shipped
- rabbitmq-cluster-operator 4.4.41 switches metrics scraping from HTTPS back to plain HTTP to avoid TLS certificate validation issues. Release
- redis 23.1.2 fixes host_id() function to include namespace, preventing identical SENTINEL MYID values when the same chart is deployed across multiple namespaces with fullnameOverride. Release
- valkey 4.0.3 refactors host_id function to include namespace, addressing the same multi-namespace deployment issue as redis. Release
Why it matters
These releases address operational issues in distributed deployments. The rabbitmq-cluster-operator fix simplifies metrics collection by removing unnecessary TLS complications, while both redis and valkey fixes prevent node identity collisions when deploying the same chart across multiple Kubernetes namespaces.
Changelog entry
- rabbitmq-cluster-operator 4.4.41: use plain HTTP instead of HTTPS for metrics scraping Release
- redis 23.1.2: patch host_id() function to include namespace for multiple cluster deployments Release
- valkey 4.0.3: refactor host_id function to include namespace Release
This week: rabbitmq-cluster-operator 4.4.41, redis 23.1.2, and valkey 4.0.3. Improvements to metrics scraping and fixes for multi-namespace cluster deployments.
Three important updates shipped this week across Bitnami charts. rabbitmq-cluster-operator 4.4.41 simplifies metrics by reverting to plain HTTP, while redis 23.1.2 and valkey 4.0.3 both fix the host_id function to properly handle multiple namespace deployments with fullnameOverride. These changes improve operational reliability in distributed Kubernetes environments.