Name: valkey-node-0 Namespace: openstack Priority: 0 Service Account: valkey Node: instance/199.204.45.61 Start Time: Sat, 22 Aug 2026 14:42:29 +0000 Labels: app.kubernetes.io/component=node app.kubernetes.io/instance=valkey app.kubernetes.io/managed-by=Helm app.kubernetes.io/name=valkey app.kubernetes.io/version=8.0.2 apps.kubernetes.io/pod-index=0 controller-revision-hash=valkey-node-85677d7b7f helm.sh/chart=valkey-2.4.6 statefulset.kubernetes.io/pod-name=valkey-node-0 Annotations: checksum/configmap: b81b16640a9b5cbcb42967e8334504c7943f51bad7074c22d15064cee2e51dff checksum/health: 79d0887a02454a7768ac61449ae806fe7c108024d5bbfdfb5f1ee21c2a80fa04 checksum/scripts: 795a40c778dbb4fd18ec228b23fa7810c0c80454b10a08e4c051ca02583789d7 checksum/secret: 44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a prometheus.io/port: 9121 prometheus.io/scrape: true Status: Running IP: 10.0.0.18 IPs: IP: 10.0.0.18 Controlled By: StatefulSet/valkey-node Containers: valkey: Container ID: containerd://a2d6be929822783c89373712dc280c6eda627cdb80619280925b3880d5a73050 Image: harbor.atmosphere.dev/docker.io/bitnamilegacy/valkey:8.0.2-debian-12-r4 Image ID: harbor.atmosphere.dev/docker.io/bitnamilegacy/valkey@sha256:ffaebb6536ea045df4b6d5b20ee3bf0cd822c27e55d32fda5dd79e487cf56d67 Port: 6379/TCP Host Port: 0/TCP SeccompProfile: RuntimeDefault Command: /bin/bash Args: -c /opt/bitnami/scripts/start-scripts/start-node.sh State: Running Started: Sat, 22 Aug 2026 14:42:35 +0000 Ready: True Restart Count: 0 Limits: cpu: 1 memory: 1Gi Requests: cpu: 500m memory: 512Mi Liveness: exec [sh -c /health/ping_liveness_local.sh 5] delay=20s timeout=5s period=5s #success=1 #failure=5 Readiness: exec [sh -c /health/ping_readiness_local.sh 1] delay=20s timeout=1s period=5s #success=1 #failure=5 Startup: exec [sh -c /health/ping_liveness_local.sh 5] delay=10s timeout=5s period=10s #success=1 #failure=22 Environment: BITNAMI_DEBUG: false VALKEY_PRIMARY_PORT_NUMBER: 6379 ALLOW_EMPTY_PASSWORD: yes VALKEY_TLS_ENABLED: yes VALKEY_TLS_PORT: 6379 VALKEY_TLS_AUTH_CLIENTS: yes VALKEY_TLS_CERT_FILE: /opt/bitnami/valkey/certs/tls.crt VALKEY_TLS_KEY_FILE: /opt/bitnami/valkey/certs/tls.key VALKEY_TLS_CA_FILE: /opt/bitnami/valkey/certs/ca.crt VALKEY_SENTINEL_TLS_ENABLED: yes VALKEY_SENTINEL_TLS_PORT_NUMBER: 26379 VALKEY_SENTINEL_TLS_AUTH_CLIENTS: yes VALKEY_SENTINEL_TLS_CERT_FILE: /opt/bitnami/valkey/certs/tls.crt VALKEY_SENTINEL_TLS_KEY_FILE: /opt/bitnami/valkey/certs/tls.key VALKEY_SENTINEL_TLS_CA_FILE: /opt/bitnami/valkey/certs/ca.crt VALKEY_DATA_DIR: /data Mounts: /data from valkey-data (rw) /health from health (rw) /opt/bitnami/scripts/start-scripts from start-scripts (rw) /opt/bitnami/valkey-sentinel/etc from sentinel-data (rw) /opt/bitnami/valkey/certs from valkey-certificates (ro) /opt/bitnami/valkey/etc from empty-dir (rw,path="app-conf-dir") /opt/bitnami/valkey/mounted-etc from config (rw) /tmp from empty-dir (rw,path="tmp-dir") sentinel: Container ID: containerd://5b38b61b205bab8777e94cdabeea0945fd32881c3f5c9278cc5cebb55b2bd10e Image: harbor.atmosphere.dev/docker.io/bitnamilegacy/valkey-sentinel:8.0.2-debian-12-r4 Image ID: harbor.atmosphere.dev/docker.io/bitnamilegacy/valkey-sentinel@sha256:dcc42519921755492973ce5c70bb06cbf73352585315511985d66b1b0d910870 Port: 26379/TCP Host Port: 0/TCP SeccompProfile: RuntimeDefault Command: /bin/bash Args: -c /opt/bitnami/scripts/start-scripts/start-sentinel.sh State: Running Started: Sat, 22 Aug 2026 14:42:43 +0000 Ready: True Restart Count: 0 Limits: cpu: 150m ephemeral-storage: 2Gi memory: 192Mi Requests: cpu: 100m ephemeral-storage: 50Mi memory: 128Mi Liveness: exec [sh -c /health/ping_sentinel.sh 5] delay=20s timeout=5s period=10s #success=1 #failure=6 Readiness: exec [sh -c /health/ping_sentinel.sh 1] delay=20s timeout=1s period=5s #success=1 #failure=6 Startup: exec [sh -c /health/ping_sentinel.sh 5] delay=10s timeout=5s period=10s #success=1 #failure=22 Environment: BITNAMI_DEBUG: false ALLOW_EMPTY_PASSWORD: yes VALKEY_SENTINEL_TLS_ENABLED: yes VALKEY_SENTINEL_TLS_PORT_NUMBER: 26379 VALKEY_SENTINEL_TLS_AUTH_CLIENTS: yes VALKEY_SENTINEL_TLS_CERT_FILE: /opt/bitnami/valkey/certs/tls.crt VALKEY_SENTINEL_TLS_KEY_FILE: /opt/bitnami/valkey/certs/tls.key VALKEY_SENTINEL_TLS_CA_FILE: /opt/bitnami/valkey/certs/ca.crt Mounts: /data from valkey-data (rw) /health from health (rw) /opt/bitnami/scripts/start-scripts from start-scripts (rw) /opt/bitnami/valkey-sentinel/etc from sentinel-data (rw) /opt/bitnami/valkey-sentinel/mounted-etc from config (rw) /opt/bitnami/valkey/certs from valkey-certificates (ro) /tmp from empty-dir (rw,path="tmp-dir") metrics: Container ID: containerd://e2db0630220a0c8d0b913c316cd464a313a2dd2e9bd9577befce1edd1da2023e Image: harbor.atmosphere.dev/docker.io/bitnamilegacy/redis-exporter:1.67.0-debian-12-r9 Image ID: harbor.atmosphere.dev/docker.io/bitnamilegacy/redis-exporter@sha256:a6727192c7499bf74d728a2f18aaff00520b0cb19b2c1bc309ae3f6a08545cf9 Port: 9121/TCP Host Port: 0/TCP SeccompProfile: RuntimeDefault Command: /bin/bash -c redis_exporter State: Running Started: Sat, 22 Aug 2026 14:42:46 +0000 Ready: True Restart Count: 0 Limits: cpu: 150m ephemeral-storage: 2Gi memory: 192Mi Requests: cpu: 100m ephemeral-storage: 50Mi memory: 128Mi Liveness: tcp-socket :metrics delay=10s timeout=5s period=10s #success=1 #failure=5 Readiness: http-get http://:metrics/ delay=5s timeout=1s period=10s #success=1 #failure=3 Environment: REDIS_ALIAS: valkey REDIS_EXPORTER_WEB_LISTEN_ADDRESS: :9121 REDIS_ADDR: valkeys://localhost:6379 REDIS_EXPORTER_TLS_CLIENT_KEY_FILE: /opt/bitnami/valkey/certs/tls.key REDIS_EXPORTER_TLS_CLIENT_CERT_FILE: /opt/bitnami/valkey/certs/tls.crt REDIS_EXPORTER_TLS_CA_CERT_FILE: /opt/bitnami/valkey/certs/ca.crt Mounts: /opt/bitnami/valkey/certs from valkey-certificates (ro) /tmp from empty-dir (rw,path="tmp-dir") Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: valkey-data: Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace) ClaimName: valkey-data-valkey-node-0 ReadOnly: false start-scripts: Type: ConfigMap (a volume populated by a ConfigMap) Name: valkey-scripts Optional: false health: Type: ConfigMap (a volume populated by a ConfigMap) Name: valkey-health Optional: false config: Type: ConfigMap (a volume populated by a ConfigMap) Name: valkey-configuration Optional: false sentinel-data: Type: EmptyDir (a temporary directory that shares a pod's lifetime) Medium: SizeLimit: empty-dir: Type: EmptyDir (a temporary directory that shares a pod's lifetime) Medium: SizeLimit: valkey-certificates: Type: Secret (a volume populated by a Secret) SecretName: valkey-server-certs Optional: false QoS Class: Burstable Node-Selectors: openstack-control-plane=enabled Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s node.kubernetes.io/unreachable:NoExecute op=Exists for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 47m default-scheduler Successfully assigned openstack/valkey-node-0 to instance Normal Pulling 47m kubelet Pulling image "harbor.atmosphere.dev/docker.io/bitnamilegacy/valkey:8.0.2-debian-12-r4" Normal Pulled 47m kubelet Successfully pulled image "harbor.atmosphere.dev/docker.io/bitnamilegacy/valkey:8.0.2-debian-12-r4" in 4.752s (4.752s including waiting) Normal Created 47m kubelet Created container valkey Normal Started 47m kubelet Started container valkey Normal Pulling 47m kubelet Pulling image "harbor.atmosphere.dev/docker.io/bitnamilegacy/valkey-sentinel:8.0.2-debian-12-r4" Normal Pulled 47m kubelet Successfully pulled image "harbor.atmosphere.dev/docker.io/bitnamilegacy/valkey-sentinel:8.0.2-debian-12-r4" in 2.436s (7.703s including waiting) Normal Created 47m kubelet Created container sentinel Normal Started 47m kubelet Started container sentinel Normal Pulling 47m kubelet Pulling image "harbor.atmosphere.dev/docker.io/bitnamilegacy/redis-exporter:1.67.0-debian-12-r9" Normal Pulled 47m kubelet Successfully pulled image "harbor.atmosphere.dev/docker.io/bitnamilegacy/redis-exporter:1.67.0-debian-12-r9" in 2.769s (2.769s including waiting) Normal Created 47m kubelet Created container metrics Normal Started 47m kubelet Started container metrics Warning Unhealthy 46m (x7 over 47m) kubelet Startup probe failed: Could not connect to Valkey at localhost:6379: Connection refused Warning Unhealthy 46m (x6 over 47m) kubelet Startup probe failed: Could not connect to Valkey at localhost:26379: Connection refused