fix(deploy): use /metrics path for SpiceDB health probes

[jsell-rh]

Summary

The previous probe change (#436) used path: / on port 9090 which returns 404. SpiceDB's metrics endpoint is at /metrics.

Verified locally: curl http://localhost:9091/metrics returns HTTP 200 on plaintext port 9090 even with gRPC TLS enabled.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated health check configuration for improved service reliability and monitoring.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 88045172-22b0-49cd-87d8-68a94734c1e4

📥 Commits

Reviewing files that changed from the base of the PR and between 6353566 and 6daca0b.

📒 Files selected for processing (1)

• deploy/apps/kartograph/base/spicedb-deployment.yaml

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting

---

Walkthrough

Modified the health check configuration for the spicedb container in the Kubernetes deployment manifest. Replaced gRPC-based probes that targeted port 50051 with HTTP-based probes that perform GET requests to the /metrics endpoint on port 9090. The change was applied to both the livenessProbe and readinessProbe fields. All existing timing and threshold parameters were preserved.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jsell/fix/spicedb-metrics-probe

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}