Give the proper reason for killing pods
Add the reason the pod was killed, e.g. exceeded memory limit, liveness probe, readiness probe... Kubelet outputs "Killing container with id docker://your-example-application:Need to kill Pod" Reason: "Killing" This message is unhelpful when it comes to diagnosing why the pod was killed, and can be improved with the reason from Kubelet to aid debugging.
Posted by andreib1 on Aug 21, 2019, 2:08 PM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
Give the proper reason for killing pods
Add the reason the pod was killed, e.g. exceeded memory limit, liveness probe, readiness probe... Kubelet outputs "Killing container with id docker://your-example-application:Need to kill Pod" Reason: "Killing" This message is unhelpful when it comes to diagnosing why the pod was killed, and can be improved with the reason from Kubelet to aid debugging.
Comments (0)
No comments yet. Start the discussion.