feat:Add PrometheusRule manifests for operational alerting

[iamdeepaktiwari08]

Problem statement

Problem

Kerno already exposes Prometheus metrics through the /metrics endpoint and includes a ServiceMonitor for scraping. However, there are currently no PrometheusRule resources for generating alerts based on these metrics.

Without alerting, operators must manually inspect metrics dashboards to detect issues.

Proposed solution

Proposed Solution

Add PrometheusRule manifests with useful operational alerts such as:

• TargetDown (metrics endpoint unavailable)

• HighPodRestartCount

• HighCPUUsage

• HighMemoryUsage

Benefits

• Faster incident detection

• Improved Kubernetes observability

• Better operational monitoring

• Complements the existing ServiceMonitor setup

Alternatives considered

No response

Scope

New CLI subcommand or flag

Affects Kubernetes deployment?

Yes — K8s-specific feature

Are you willing to contribute?

• I can implement this if guidance is provided
• I can test this once it's built
• I'm just suggesting the idea

[pri265126-stack]

Hi Mentors,
I am interested in working on this issue.
Could you please assign it to me?

[github-actions]

Hey @pri265126-stack, welcome. Looks like this is your first comment in the repo.

Want to work on this issue? Reply with /assign or /take to claim it.

If the work's been useful, two quick ways to help:

⭐ Star kerno: eBPF kernel diagnosis engine
⭐ Star optiqor-cli: Kubernetes cost remediation that lives in the pull request

Thanks for showing up.

[taneesha-reyyi]

@optiqor

Hello, I would like to work on this issue under GSSoC'26.

I am interested in implementing PrometheusRule manifests for operational alerting to improve observability, proactive monitoring, and Kubernetes operational reliability for the project.

My Planned Approach

• Analyze the existing Prometheus metrics exposure and current ServiceMonitor setup to understand available monitoring data and integration points.
• Create dedicated PrometheusRule manifests containing operational alerts such as:

• TargetDown
• HighPodRestartCount
• HighCPUUsage
• HighMemoryUsage
  • Define meaningful alert thresholds and severity levels to reduce noisy or unnecessary alerts while ensuring critical issues are detected early.
  • Structure alert rules following Prometheus/Kubernetes best practices for readability and maintainability.
  • Ensure compatibility with the existing monitoring stack and Kubernetes deployment architecture.
  • Add descriptive annotations and labels for:
• Alert summaries
• Operational context
• Troubleshooting guidance
  • Validate alert expressions against exposed /metrics data to ensure accuracy and proper triggering behavior.
  • Test the manifests in a Kubernetes environment to verify:
• Rule loading
• Alert triggering
• Stability
• Resource compatibility
  • Maintain modular and extensible alert configuration so additional operational alerts can be added easily in the future.

Expected Outcome

The project will gain proactive operational alerting capabilities, enabling faster incident detection, improved Kubernetes observability, and more reliable monitoring for runtime and infrastructure health.

I can start working on this immediately and will follow the project architecture and contribution guidelines properly.

Kindly assign this issue to me.

[github-actions]

Hey @taneesha-reyyi, welcome. Looks like this is your first comment in the repo.

Want to work on this issue? Reply with /assign or /take to claim it.

If the work's been useful, two quick ways to help:

⭐ Star kerno: eBPF kernel diagnosis engine
⭐ Star optiqor-cli: Kubernetes cost remediation that lives in the pull request

Thanks for showing up.

[iamdeepaktiwari08]

@btwshivam
Hi, I am still interested in working on this issue. I have reviewed the existing monitoring setup and would be happy to implement the proposed PrometheusRule manifests if the issue is available.

Could you please assign this issue to me?

[iamdeepaktiwari08]

/assign

[github-actions]

Assigned to @iamdeepaktiwari08. Thanks for picking this up! 🚀

Heads-up: if there's no activity (comment or PR linked here) within 10 days, the issue will be auto-released so others can pick it up. Comment any time to reset that timer.

Need help getting started? Check CONTRIBUTING.md or ask in the issue thread.

[github-actions]

Hi @iamdeepaktiwari08 — heads up that this issue has had no activity from you in 7 days.

If you're still working on it, leave a comment and the timer resets. Otherwise it'll be auto-released in 3 days so others can pick it up.

Need help getting unstuck? Reply here, no judgement.

[iamdeepaktiwari08]

i have done this work and made a pr but review still pending on the pr
feat: add PrometheusRule manifests for operational alerting
#209