-
-
Notifications
You must be signed in to change notification settings - Fork 35
Closed
Labels
bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.needs-priorityIndicates a PR lacks a label and requires one.Indicates a PR lacks a label and requires one.needs-triageIndicates an issue or PR lacks a label and requires one.Indicates an issue or PR lacks a label and requires one.
Description
What happened:
INFO: 240.243.170.78:33428 - "GET /health HTTP/1.1" 200 OK
INFO: 240.243.170.78:33438 - "GET /health_generate HTTP/1.1" 404 Not Found
INFO: 240.243.170.78:42582 - "GET /health_generate HTTP/1.1" 404 Not Found
INFO: 240.243.170.78:42596 - "GET /health_generate HTTP/1.1" 404 Not Found
INFO: 240.243.170.78:42624 - "GET /health_generate HTTP/1.1" 404 Not Found
INFO: 240.243.170.78:42608 - "GET /health HTTP/1.1" 200 OK
What you expected to happen:
The SGLang pod is in ready status.
How to reproduce it (as minimally and precisely as possible):
Deploy SGLand playground example
Anything else we need to know?:
Environment:
- Kubernetes version (use
kubectl version
): v1.30.8 - llmaz version (use
git describe --tags --dirty --always
): 0.0.9 - Cloud provider or hardware configuration:
- OS (e.g:
cat /etc/os-release
): - Kernel (e.g.
uname -a
): - Install tools:
- Others:
Metadata
Metadata
Assignees
Labels
bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.needs-priorityIndicates a PR lacks a label and requires one.Indicates a PR lacks a label and requires one.needs-triageIndicates an issue or PR lacks a label and requires one.Indicates an issue or PR lacks a label and requires one.