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

OOM trigger #51

Open
samisevenx00 opened this issue Jan 23, 2022 · 3 comments
Open

OOM trigger #51

samisevenx00 opened this issue Jan 23, 2022 · 3 comments
Assignees

Comments

@samisevenx00
Copy link

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

The Idea Is to détect and alert when pod was killed by Out or memory.

Describe the solution you'd like
A clear and concise description of what you want to happen.

@simonfrey
Copy link
Collaborator

This already exists, doesn't it?

DeepinScreenshot_select-area_20220124184046

@tdslot
Copy link

tdslot commented Jan 25, 2022

Hello,

Does it OOMKilled works? Yesterday I installed and at night I had couple OOMKilled pods, I see in logs, but kwatch didn't reported. Maybe need some how turn on notification in configuration?

Maybe kwatch need some version of Kubernetes to detects OOMKilled pods?

@electrical
Copy link

I just installed this on our cluster ( Kubernetes 1.19.15 ) and received an OOMKilled notification as expected.

@abahmed abahmed added this to kwatch Sep 19, 2022
@abahmed abahmed moved this to 📋 Backlog in kwatch Sep 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📋 Backlog
Development

No branches or pull requests

5 participants