Name: valkey-node-0 Namespace: openstack Priority: 0 Service Account: valkey Node: instance/199.19.213.219 Start Time: Fri, 20 Mar 2026 10:17:09 +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.95 IPs: IP: 10.0.0.95 Controlled By: StatefulSet/valkey-node Containers: valkey: Container ID: containerd://17bd5e7e6f4d45412d27ff8ac2311274f3b99ae054dbc10541af55141e045ed7 Image: harbor.atmosphere.dev/docker.io/bitnamilegacy/valkey:8.0.2-debian-12-r4 Image ID: harbor.atmosphere.dev/docker.io/bitnamilegacy/valkey@sha256:2e2461283571a3e70a784fdab52f6d64f133cb6adff3b0b1644baa10a638666e 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: Fri, 20 Mar 2026 10:17:13 +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://6e33ecc74a8d1355761fb34f52896e9d236c370015e6bef08462040b0441b5a1 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:867272e72712b492b1885129f8167e378283636720176c2cd63df91cc9e080ae 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: Fri, 20 Mar 2026 10:17:17 +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://eedf5b062fb3113f10506f9f4d6fba0cad0d2b76eac62ad3a5eb3dc90514a59f 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:ed4ce7abc3bb5cd058d4308407fdb0bb1a241a9d09db9a784b92e9edd7288a4c Port: 9121/TCP Host Port: 0/TCP SeccompProfile: RuntimeDefault Command: /bin/bash -c redis_exporter State: Running Started: Fri, 20 Mar 2026 10:17:25 +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 5m45s default-scheduler Successfully assigned openstack/valkey-node-0 to instance Normal Pulling 5m44s kubelet Pulling image "harbor.atmosphere.dev/docker.io/bitnamilegacy/valkey:8.0.2-debian-12-r4" Normal Pulled 5m41s kubelet Successfully pulled image "harbor.atmosphere.dev/docker.io/bitnamilegacy/valkey:8.0.2-debian-12-r4" in 3.144s (3.144s including waiting) Normal Created 5m41s kubelet Created container valkey Normal Started 5m41s kubelet Started container valkey Normal Pulling 5m41s kubelet Pulling image "harbor.atmosphere.dev/docker.io/bitnamilegacy/valkey-sentinel:8.0.2-debian-12-r4" Normal Pulled 5m38s kubelet Successfully pulled image "harbor.atmosphere.dev/docker.io/bitnamilegacy/valkey-sentinel:8.0.2-debian-12-r4" in 3.049s (3.049s including waiting) Normal Created 5m37s kubelet Created container sentinel Normal Started 5m37s kubelet Started container sentinel Normal Pulling 5m37s kubelet Pulling image "harbor.atmosphere.dev/docker.io/bitnamilegacy/redis-exporter:1.67.0-debian-12-r9" Normal Pulled 5m29s kubelet Successfully pulled image "harbor.atmosphere.dev/docker.io/bitnamilegacy/redis-exporter:1.67.0-debian-12-r9" in 2.982s (8.025s including waiting) Normal Created 5m29s kubelet Created container metrics Normal Started 5m29s kubelet Started container metrics Warning Unhealthy 4m34s (x6 over 5m24s) kubelet Startup probe failed: Could not connect to Valkey at localhost:26379: Connection refused Warning Unhealthy 4m24s (x7 over 5m24s) kubelet Startup probe failed: Could not connect to Valkey at localhost:6379: Connection refused