-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Add codes for error types and detect terminated containers #4012
Conversation
proto/skaffold.proto
Outdated
@@ -231,4 +231,25 @@ enum ErrorCode { | |||
// COULD_NOT_GET_DOCKER_CLIENT = 7; | |||
// COULD_NOT_GET_LOCAL_CLUSTER = 8; | |||
// BUILDER_CLEANUP = 9; | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we could follow grouping by first digit similar to HTTP status codes (https://www.rfc-editor.org/rfc/rfc7231.txt)
I like the container errors being 3xx, and k8s infra errors 4xx, but then NO_ERROR should be 2xx, unknown 5xx, e.g. (unknown 500, unknown unsched 501) WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sounds good. i have tried to group them, but not to the best!
Please visit http://34.94.185.45:1313 to view changes to the docs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with nits:
- docs on error codes
- error code numbering
Please visit http://34.94.41.154:1313 to view changes to the docs. |
Please visit http://34.94.185.45:1313 to view changes to the docs. |
Please visit http://34.94.41.154:1313 to view changes to the docs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Related #3952
In this change, Diagnostic library will now return an error code for each error type e. g "ImgPullErr" or "RunContainerErr"
Skaffold pod health check will consume this error code and propogate it to IDEs in
ResourceStatusCheckEvent
for them to determine what next actions could be taken.Description
User facing changes (remove if N/A)
None.
Follow-up Work (remove if N/A)
Add
ErrorCode
toResourceStatusCheckEvent
protoHook up pod health check in
pkg/diag
with skaffold.