derailed/popeye

👀 A Kubernetes cluster resource sanitizer

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 42 minutes ago
Added to GitGenius on September 10th, 2026
Created on March 18th, 2019
Open Issues & Pull Requests: 68 (+0)
GitHub issues: Enabled
Number of forks: 346
Total Stargazers: 6,361 (+0)
Total Subscribers: 48 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 27.5 days
Mean response time: 195.5 days
90th percentile: 761.4 days
Tracked items: 43

How this project is maintained

100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 94% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 27
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 551 days
Stale 30+ days: 27
Stale 90+ days: 26

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (11)
  • question (11)
  • asDesigned (7)
  • enhancement (6)
  • documentation (2)
  • no-repro (2)
  • good first issue (1)
  • performance (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Popeye is a Kubernetes cluster resource sanitizer that scans live clusters to identify misconfigurations, stale resources, and deviations from best practices.

The tool addresses the challenge of tracking deployed resources and policies in growing Kubernetes environments by analyzing what is actually running in a cluster rather than examining manifests on disk. It performs linting across curated Kubernetes resource types, detecting issues such as port mismatches, unused resources, metric utilization problems, missing probes, container image concerns, and RBAC misconfigurations. When a metric-server is present, it also reports resource over- and under-allocation and warns of potential capacity exhaustion. Popeye operates in read-only mode and does not modify any cluster resources.

Popeye suits operators and platform teams managing live Kubernetes clusters who need visibility into configuration quality and resource health. It works best for teams that want to enforce best practices across their deployments and reduce operational overhead. The tool outputs results in multiple formats including console, JSON, and HTML, and can publish Prometheus metrics for integration with monitoring systems like Grafana.

The project receives most of its issue reports from external users rather than the core team, indicating a substantial adopter base providing real-world feedback. Response times to issues and pull requests often extend beyond several weeks. The issue tracker is primarily populated with questions, bug reports, and discussions about intended behavior.