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

Improve JobFailedEvent messages #519

Merged
merged 4 commits into from
Feb 22, 2021
Merged

Improve JobFailedEvent messages #519

merged 4 commits into from
Feb 22, 2021

Conversation

JamesMurkin
Copy link
Contributor

Now properly reports pod level errors

  • Such as evicted

Now contains ContainerStatuses

  • In the same way Kubernetes does for now (i.e not always present, depends on failure). We could just generate a status for every container
  • Status contains "Message" field which contains custom error messages send to /dev/termination-log, the same as the message field in kubernetes

Now contains Pod level and container level (when present) Cause enum, which tries to give a summary idea of the pod/container failure cause. We can extend this more causes in the future (node failure etc).

Now properly reports pod level errors
 - Such as evicted

Now contains ContainerStatuses
 - In the same way Kubernetes does for now (i.e not always present, depends on failure). We could just generate a status for every container
 - Status contains "Message" field which contains custom error messages send to /dev/termination-log, the same as the message field in kubernetes

Now contains Pod level and container level (when present) Cause enum, which tries to give a summary idea of the pod/container failure cause. We can extend this more causes in the future (node failure etc).
@JamesMurkin JamesMurkin merged commit db895c2 into master Feb 22, 2021
@JamesMurkin JamesMurkin deleted the raw_error_message branch February 22, 2021 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants