mirror of
https://github.com/agent-substrate/substrate.git
synced 2026-11-11 10:23:17 +08:00
- `docs/observability.md`: log label keys were wrong. The code emits `ate.dev/actor_id` and `ate.dev/actor_template_name`; the doc had `actor_id` and `actor_template`. The Cloud Logging queries would return no results. - `docs/dev/best-practices/tracing.md`: container ports entry used Docker Compose syntax (`"443:443"`). Changed to `containerPort: 443`. - `docs/dev/valkey-direct-access.md`: the `kubectl exec` command had a line break inside `--cert`, making it fail on copy-paste. - `code-of-conduct.md`: linked to Contributor Covenant v1.4. Updated to v2.1.
543 B
543 B
Accessing valkey directly
Valkey is the state store used by ate-api-server to track actor and worker records. Direct access is useful for debugging state issues.
Warning: Avoid destructive commands (
FLUSHALL,DEL, etc.) on a live cluster.
To open a valkey-cli session:
kubectl exec -n=ate-system -it valkey-cluster-0 -- valkey-cli -h valkey-cluster-service -c --tls --cacert /etc/valkey-ca/ca.crt --cert /run/servicedns.podcert.ate.dev/credential-bundle.pem --key /run/servicedns.podcert.ate.dev/credential-bundle.pem