Add explicit k8s failure reasons to logs

[avishniakov]

Describe changes

I implemented the extended logging for reasons of various infra/config related k8s pod failures. Like OOMKilled or bad YAML definitions. With this change it will be much easier for developer to understand the reasons of each failure they face.

Examples:

• Pod died from OOMKilled:

Step log_stuff has started.
Job for step log_stuff failed. Reason: OOMKilled(exit_code=137)
Node log_stuff failed: Job xyz:dab4c163-log-stuff-test-delete failed: Job has reached the specified backoff limit

• Orchestrator pod failed to start due to bad config:

Failed to create Kubernetes orchestrator pod. Retrying in 60 seconds...
Reason: Pod "test-delete-4abd67a467cef5d12f155e549c1295c2" is invalid: [spec.containers[0].resources.limits[storage]: Invalid value: storage: must be a standard resource for containers, spec.containers[0].resources.requests[storage]: Invalid value: storage: must be a standard resource for containers]

• Step pod failed to start due to bad config (this comes not from my changes):

kubernetes.client.exceptions.ApiException: (422)
Reason: Unprocessable Entity
HTTP response headers: HTTPHeaderDict({'Audit-Id': '6463631e-bfa4-4ff6-8c39-7bc17ea6aeb5', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Kubernetes-Pf-Flowschema-Uid': '040928ca-fb88-4888-8974-037b52a948cf', 'X-Kubernetes-Pf-Prioritylevel-Uid': '1acf0369-6c22-41b2-b5d9-a0972fd8a8e8', 'Date': 'Fri, 18 Jul 2025 09:42:51 GMT', 'Content-Length': '566'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Job.batch \"1727bfbc-log-stuff-test-delete\" is invalid: spec.template.spec.containers[0].resources.limits[storage]: Invalid value: storage: must be a standard resource for containers","reason":"Invalid","details":{"name":"1727bfbc-log-stuff-test-delete","group":"batch","kind":"Job","causes":[{"reason":"FieldValueInvalid","message":"Invalid value: storage: must be a standard resource for containers","field":"spec.template.spec.containers[0].resources.limits[storage]"}]},"code":422}

Pre-requisites

Please ensure you have done the following:

• I have read the CONTRIBUTING.md document.
• I have added tests to cover my changes.
• I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
• IMPORTANT: I made sure that my changes are reflected properly in the following resources:
  • ZenML Docs
  • Dashboard: Needs to be communicated to the frontend team.
  • Templates: Might need adjustments (that are not reflected in the template tests) in case of non-breaking changes and deprecations.
  • Projects: Depending on the version dependencies, different projects might get affected.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Other (add details above)

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[schustmi]

@avishniakov This is still failing the linting, otherwise looks good to me

[avishniakov]

@avishniakov This is still failing the linting, otherwise looks good to me

Thanks @schustmi , missed that one need to do scripts/format.sh and not scripts/lint.sh 🙂
Shall be fixed now