NAME: valkey
LAST DEPLOYED: Fri Apr 24 14:25:06 2026
NAMESPACE: openstack
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
CHART NAME: valkey
CHART VERSION: 2.4.6
APP VERSION: 8.0.2

Did you know there are enterprise versions of the Bitnami catalog? For enhanced secure software supply chain features, unlimited pulls from Docker, LTS support, or application customization, see Bitnami Premium or Tanzu Application Catalog. See https://www.arrow.com/globalecs/na/vendors/bitnami for more information.

** Please be patient while the chart is being deployed **

Valkey can be accessed via port 6379 on the following DNS name from within your cluster:

    valkey.openstack.svc.cluster.local for read only operations

For read/write operations, first access the Valkey Sentinel cluster, which is available in port 26379 using the same domain name above.



To connect to your Valkey server:

1. Run a Valkey pod that you can use as a client:

   kubectl run --namespace openstack valkey-client --restart='Never'  --image harbor.atmosphere.dev/docker.io/bitnamilegacy/valkey:8.0.2-debian-12-r4 --command -- sleep infinity

   Copy your TLS certificates to the pod:

   kubectl cp --namespace openstack /path/to/client.cert valkey-client:/tmp/client.cert
   kubectl cp --namespace openstack /path/to/client.key valkey-client:/tmp/client.key
   kubectl cp --namespace openstack /path/to/CA.cert valkey-client:/tmp/CA.cert

   Use the following command to attach to the pod:

   kubectl exec --tty -i valkey-client \
   --namespace openstack -- bash

2. Connect using the Valkey CLI:
   valkey-cli -h valkey -p 6379 --tls --cert /tmp/client.cert --key /tmp/client.key --cacert /tmp/CA.cert # Read only operations
   valkey-cli -h valkey -p 26379 --tls --cert /tmp/client.cert --key /tmp/client.key --cacert /tmp/CA.cert # Sentinel access

To connect to your database from outside the cluster execute the following commands:

    kubectl port-forward --namespace openstack svc/valkey 6379:6379 &
    valkey-cli -h 127.0.0.1 -p 6379 --tls --cert /tmp/client.cert --key /tmp/client.key --cacert /tmp/CA.cert

WARNING: There are "resources" sections in the chart not set. Using "resourcesPreset" is not recommended for production. For production installations, please set the following values according to your workload needs:
  - metrics.resources
  - sentinel.resources
+info https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/

⚠ SECURITY WARNING: Original containers have been substituted. This Helm chart was designed, tested, and validated on multiple platforms using a specific set of Bitnami and Tanzu Application Catalog containers. Substituting other containers is likely to cause degraded security and performance, broken chart features, and missing environment variables.

Substituted images detected:
  - harbor.atmosphere.dev/docker.io/bitnamilegacy/valkey:8.0.2-debian-12-r4
  - harbor.atmosphere.dev/docker.io/bitnamilegacy/valkey-sentinel:8.0.2-debian-12-r4
  - harbor.atmosphere.dev/docker.io/bitnamilegacy/redis-exporter:1.67.0-debian-12-r9

⚠ SECURITY WARNING: Verifying original container images was skipped. Please note this Helm chart was designed, tested, and validated on multiple platforms using a specific set of Bitnami and Tanzu Application Catalog containers. Substituting other containers is likely to cause degraded security and performance, broken chart features, and missing environment variables.