Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Return 503 when service has no ready endpoints #2430

Closed
kate-osborn opened this issue Aug 20, 2024 · 0 comments · Fixed by #2696
Closed

Return 503 when service has no ready endpoints #2430

kate-osborn opened this issue Aug 20, 2024 · 0 comments · Fixed by #2696
Assignees
Labels
bug Something isn't working refined Requirements are refined and the issue is ready to be implemented. size/extra-small Estimated to be completed within a day
Milestone

Comments

@kate-osborn
Copy link
Contributor

According to the spec:

When a HTTPBackendRef refers to a Service that has no ready endpoints, implementations SHOULD return a 503 for requests to that backend instead.

Currently, NGF returns a 502.

A/C:

  • NGF should return a 503 when a service has no ready endpoints.
@mpstefan mpstefan added the bug Something isn't working label Aug 27, 2024
@mpstefan mpstefan added this to the v1.5.0 milestone Aug 27, 2024
@mpstefan mpstefan added refined Requirements are refined and the issue is ready to be implemented. size/extra-small Estimated to be completed within a day labels Oct 7, 2024
@bjee19 bjee19 self-assigned this Oct 16, 2024
@lucacome lucacome moved this to ✅ Done in NGINX Gateway Fabric Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working refined Requirements are refined and the issue is ready to be implemented. size/extra-small Estimated to be completed within a day
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants