Lookout API: Take empty Kubernetes (Pod) IDs into account when processing failed events #499
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When reporting failed events, a Kubernetes ID for a given Job might not exist if a Pod is yet to be created (if the job fails before the Pod is created).
This is a problem in the Lookout API, as the database uses this Kubernetes ID as key for one of its tables (
job_run
).To fix this, we generate an artificial ID for the Job.