Arize AI Community Icon

Home
Events

Arize AX Releases
Arize AX Support
Arize News
Arize Observe
Discussions
Introductions
Phoenix Support

Powered by Tightknit

Phoenix Support

Recommendations for Kubernetes Probes with Phoenix Deployment | Arize AI Community

Phoenix Support

Recommendations for Kubernetes Probes with Phoenix Deployment

·Oct 08, 2024 01:57 AM

Hi there! I’m seeking recommendations for readiness and liveness probes when deploying Phoenix in Kubernetes 🧵

3 comments

· Sorted by Oldest

RunLLM
APP
·
For readiness and liveness probes when deploying Phoenix in Kubernetes, you can use the /healthz endpoint for health checks. This endpoint was added specifically for health checks in Phoenix.**Example Kubernetes Configuration::**LBKSLBKS```LBKSapiVersion:: apps/v1 kind: StatefulSet metadata: name: phoenix namespace: phoenix spec: replicas: 1 selector: matchLabels: app: phoenix template: metadata: labels: app: phoenix spec: containers: - name: phoenix image: arizephoenix/phoenix::latest ports:: - containerPort: 6006 - containerPort: 4317 readinessProbe: httpGet: path: /healthz port: 6006 initialDelaySeconds: 10 periodSeconds: 5 livenessProbe: httpGet: path: /healthz port: 6006 initialDelaySeconds: 30 periodSeconds: 10```This configuration sets up both readiness and liveness probes to check the /healthz endpoint on port 6006.Would you like more details on any specific part of this setup?Sources: - chore: add /healthz route for healthchecks
💡 Hint: Mention RunLLM in the thread for followups.
Elliot P.
·
/healthz seems reasonable for a liveness check. However, it might not be sufficient for a readiness check. Do you recommend the root path (/ on PHOENIX_PORT) for a readiness check?
Elliot P.
·
Thank you, Mikyo! Really appreciate the help