redis-client-layer
| Version | 2026.144.1443 |
| Repo | superproject |
harness-redis-client — installs redis-cli for cross-pod redis access
Provides /usr/bin/redis-cli so the harness can run
redis-cli -h charly-redis SET ... and verify cross-pod connectivity.
No redis service is started in this image — it acts purely as a client.
Services
Section titled “Services”keep-alive
Acceptance plan
Section titled “Acceptance plan”This candy’s plan: — the runnable spec charly check executes against a live deployment. check: steps are idempotent probes; run: steps change state.
| Intent | Step |
|---|---|
check |
the redis-cli client binary is installed at /usr/bin/redis-cli |
check |
the redis package that provides redis-cli is installed (valkey-compat-redis on Fedora 43) |
check |
redis-cli actually runs and reports a version |
check |
the ss socket-inspection tool from iproute is installed at /usr/sbin/ss |
check |
the pgrep process tool from procps-ng is installed at /usr/bin/pgrep |
check |
the keep-alive supervised service is running in the deployed pod |
agent-check |
the keep-alive service keeps the client pod alive, auto-restarting (restart=always) if it exits, so the harness can keep issuing cross-pod redis-cli probes against a separate redis pod |