redis-server-layer
| Version | 2026.144.1443 |
| Repo | superproject |
harness-redis-server — redis-server bound to 0.0.0.0 for cross-pod access
Runs /usr/bin/redis-server (provided by valkey-compat-redis on Fedora 43)
bound to 0.0.0.0:6379 with protected-mode off, so a sibling redis-client
pod on the shared charly network can SET/GET via redis-cli -h charly-redis.
Services
Section titled “Services”redis-server
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 |
|---|---|
run |
mkdir=/var/lib/harness-redis |
check |
the redis-server daemon binary is present at /usr/bin/redis-server |
check |
the redis-cli client binary is present at /usr/bin/redis-cli |
check |
the redis package (valkey-compat-redis on Fedora 43) is installed |
check |
the running redis-server answers PING with PONG on port 6379 |
check |
the published redis TCP port is reachable from the host |
agent-check |
redis-server-layer is deployed with –bind 0.0.0.0 and protected-mode off |
agent-check |
a sibling redis-client pod on the shared charly network connects to charly-redis:6379 |
agent-check |
the sibling pod can SET and GET keys against this redis instance |
check |
service=redis-server |
check |
port=6379 |