generated from kubernetes/kubernetes-template-project
-
Notifications
You must be signed in to change notification settings - Fork 490
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
Move error status code to 500 #1200
Comments
youngnick
added
the
kind/feature
Categorizes issue or PR as related to a new feature.
label
Jun 10, 2022
@youngnick This needs to be done only in |
I would like to take up this one. |
In both please, we will keep the v1alpha2 and v1beta1 in sync for this release. |
We agreed that:
@mikemorris is going to write out a list of the different cases, and check we haven't missed anything. |
youngnick
changed the title
Move error status code to 502
Move error status code to 500
Jun 13, 2022
/assign |
This was referenced Jun 14, 2022
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be added:
In various places, we've documented that having no endpoints available should variously be 404 or 503. @thockin suggested in the v0.5.0 API Review that we should consider 502 instead.
This issue covers agreeing that's the case, and then implementing that change.
Why this is needed:
Need to get breaking behavior changes done before we release v0.5.0.
The text was updated successfully, but these errors were encountered: