You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when the server is started with an api-key, the /health endpoint also requires the api-key for requests.
Some cloud services' health check functions cannot set authentication information for requests, causing issues with deployment health checks.
Is it possible to remove the authentication check from the /health endpoint?
For reference, in vllm, the /health endpoint does not require authentication.
Related resources
No response
The text was updated successfully, but these errors were encountered:
What I would like to achieve is to have api-key authentication for inference endpoints (e.g., /v1/completions), but allow the /health endpoint to respond with a 200 status without requiring authentication.
Motivation
Currently, when the server is started with an api-key, the /health endpoint also requires the api-key for requests.
Some cloud services' health check functions cannot set authentication information for requests, causing issues with deployment health checks.
Is it possible to remove the authentication check from the /health endpoint?
For reference, in vllm, the /health endpoint does not require authentication.
Related resources
No response
The text was updated successfully, but these errors were encountered: