Error Handling

The API uses standard HTTP status codes to indicate the success or failure of requests. Common error codes include:

• 400 Bad Request: The request was invalid or cannot be served.

• 401 Unauthorized: Authentication failed or user does not have permissions for the requested operation.

• 403 Forbidden: The request is understood, but it has been refused or access is not allowed.

• 404 Not Found: The requested resource could not be found.

• 500 Internal Server Error: Something went wrong on the server.

Note

If you see intermittent 500 responses under concurrent load, with Connector is closed in the service log, upgrade to 1.12.1 or later, where the Kubernetes client is long-lived and initialized once.

In case of an error, the response body contains more details about the error:

{
  "detail": "Error message describing the issue"
}

Remember that proper error handling, logging, and monitoring should be implemented to help diagnose and resolve issues quickly.