You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am planning to perform manual Kubernetes testing on the node-problem-detector image (installed via Helm) to simulate node issues, similar to problem-maker. However, if I understand correctly, problem-maker cannot be used for image-based testing.
I wanted to check if there is an alternative approach to manually test the node-problem-detector image and validate its functionality.
For a comprehensive test, we aim to cover:
Simulating Node Problems – Ensuring NPD detects and reports issues such as OOM kills, Docker daemon hangs, etc.
Prometheus Metrics Testing – Verifying that NPD correctly exports metrics related to node problems for monitoring systems.
This is similar to e2e testing, but I haven’t found any clear workarounds specifically for testing the node-problem-detector image. Are there any recommended methods or existing approaches that I'm missing out? Sorry if similar issue has been raised before.
Any guidance or suggestions would be greatly appreciated!!
The text was updated successfully, but these errors were encountered:
sanjayk0508
changed the title
Support for simulating/generating node problems in node-problem-detector Image testing
simulating node problems for Image testing
Feb 18, 2025
I am planning to perform manual Kubernetes testing on the
node-problem-detector
image (installed via Helm) to simulate node issues, similar toproblem-maker
. However, if I understand correctly,problem-maker
cannot be used for image-based testing.I wanted to check if there is an alternative approach to manually test the
node-problem-detector
image and validate its functionality.For a comprehensive test, we aim to cover:
This is similar to e2e testing, but I haven’t found any clear workarounds specifically for testing the
node-problem-detector
image. Are there any recommended methods or existing approaches that I'm missing out? Sorry if similar issue has been raised before.Any guidance or suggestions would be greatly appreciated!!
The text was updated successfully, but these errors were encountered: