Services expose readiness only over custom HTTP or contract probes, so standard gRPC health checking and health-aware balancing (e.g. under Kubernetes or a mesh) cannot be used. Done when each gRPC server registers grpc.health.v1 driven by its readiness probes. Wait for a real consumer before building.
Close reason
No consumer: no Kubernetes/mesh deployment or client uses grpc.health.v1; services already report readiness through their own probes. Refile if one appears.
Imported from beads archie-core-5zseu · GitHub #1726 · type task · priority P4 · created 2026-10-15 · closed 2026-10-25
Services expose readiness only over custom HTTP or contract probes, so standard gRPC health checking and health-aware balancing (e.g. under Kubernetes or a mesh) cannot be used. Done when each gRPC server registers grpc.health.v1 driven by its readiness probes. Wait for a real consumer before building.
### Close reason
No consumer: no Kubernetes/mesh deployment or client uses grpc.health.v1; services already report readiness through their own probes. Refile if one appears.
---
_Imported from beads `archie-core-5zseu` · GitHub #1726 · type task · priority P4 · created 2026-10-15 · closed 2026-10-25_
sam
added the task label 2026-10-27 13:38:59 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Services expose readiness only over custom HTTP or contract probes, so standard gRPC health checking and health-aware balancing (e.g. under Kubernetes or a mesh) cannot be used. Done when each gRPC server registers grpc.health.v1 driven by its readiness probes. Wait for a real consumer before building.
Close reason
No consumer: no Kubernetes/mesh deployment or client uses grpc.health.v1; services already report readiness through their own probes. Refile if one appears.
Imported from beads
archie-core-5zseu· GitHub #1726 · type task · priority P4 · created 2026-10-15 · closed 2026-10-25