Add Kubernetes node problem detector

[BigBen-7]

Description

Deploy node problem detector for early hardware issue detection.

Requirements

• NPD DaemonSet deployment
• Custom problem definitions
• Alert rules for node problems
• Automatic node cordoning
• Incident creation integration

Files to Touch

• infrastructure/k8s/node-problem-detector/daemonset.yaml
• infrastructure/k8s/node-problem-detector/config.yaml
• infrastructure/monitoring/node-alerts.yml

Complexity: 250 points

[anilyagiz]

Hi, I’d like to apply for this issue.

I have around 5 years of experience as a software developer, with hands-on experience in backend systems, Kubernetes-based deployments, infrastructure automation, CI/CD workflows, monitoring, alerting, and production reliability. I have worked on systems where early detection of infrastructure problems, clear operational signals, and automated recovery workflows were important for keeping services stable.

For this issue, I would start by reviewing the current Kubernetes cluster structure, node labels, monitoring setup, and any existing alert or incident management integrations. Then I would deploy Node Problem Detector as a DaemonSet under infrastructure/k8s/node-problem-detector/daemonset.yaml so every node can continuously report kernel, runtime, disk, network, and system-level problems.

I would configure infrastructure/k8s/node-problem-detector/config.yaml with suitable custom problem definitions for the project’s environment. This could include checks for disk pressure, filesystem errors, kernel deadlocks, container runtime issues, kubelet problems, network instability, and recurring system log patterns that may indicate hardware or node-level degradation.

For monitoring, I would add alert rules in infrastructure/monitoring/node-alerts.yml so node problems are surfaced quickly with clear severity levels. The alerts would include useful context such as node name, condition type, affected component, first seen time, and suggested next action, making them easier to triage during incidents.

I would also implement automatic node cordoning for serious node problems where continuing to schedule workloads would create risk. The cordoning logic would be scoped carefully to avoid unnecessary disruption, and I would ensure it works together with existing Kubernetes scheduling, draining, and recovery practices.

For incident creation, I would connect critical node problem alerts to the existing incident workflow so the team can respond quickly when hardware or system-level failures are detected. This would help turn node health signals into actionable operational events instead of leaving them buried in logs.

Finally, I would add documentation covering the DaemonSet deployment, custom problem definitions, alert behavior, cordoning criteria, incident integration, and troubleshooting steps. My goal would be to deliver a reliable node problem detection setup that helps PinSpace identify infrastructure risks early and reduce production impact from unhealthy Kubernetes nodes.

[omonxooo-commits]

@omonxooo-commits has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would love to work on this project. I promise to deliver

ℹ️ Repo Maintainers: To accept this application, review their application or assign @omonxooo-commits to this issue.

[Creative-Titilayo]

@Creative-Titilayo has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I'd like to work on this issue. I've gone through the description and acceptance criteria and I'm confident I can deliver it. I'll make sure every acceptance criterion is met and submit a clean, tested PR. Please assign it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Creative-Titilayo to this issue.

[portableDD]

@portableDD has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

can i handle this issue?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @portableDD to this issue.

[drips-wave]

Congratulations, @portableDD! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @portableDD: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🦊 GrantFox — @portableDD has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #707)
2. Your PR will be reviewed by the PinSpace-Org maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

This issue has been completed by @portableDD as part of the Stellar Wave Program's 6th Wave 🥳

😎 @portableDD: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.