doitintl/kube-no-trouble

Easily check your clusters for use of deprecated APIs

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 6 minutes ago
Added to GitGenius on September 18th, 2026
Created on April 8th, 2020
Open Issues & Pull Requests: 30 (+0)
GitHub issues: Enabled
Number of forks: 169
Total Stargazers: 3,679 (+0)
Total Subscribers: 14 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 19.0 days
Mean response time: 93.9 days
90th percentile: 376.7 days
Tracked items: 20

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 12
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,140 days
Stale 30+ days: 12
Stale 90+ days: 12

Recent activity

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

Top labels

  • not-stale (16)
  • stale (11)
  • good-first-issue (9)
  • bug (7)
  • docs (3)
  • feature (3)
  • refactor (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Kube-No-Trouble is a command-line tool that checks Kubernetes clusters for use of deprecated APIs.

The tool solves the problem of identifying deprecated API usage before upgrading a Kubernetes cluster, which can cause workload failures if not addressed first. It works by scanning resources in your cluster and comparing them against known deprecations. The tool can detect deprecated APIs from multiple sources: local YAML or JSON manifests, resources deployed via kubectl that have the last-applied-configuration annotation, and Helm v3 releases stored as Secrets or ConfigMaps in cluster namespaces.

The tool suits operators and cluster administrators preparing for Kubernetes upgrades. It works best when resources have been deployed through kubectl or Helm, since it relies on stored manifests to detect deprecations. For teams managing manifests as files, the tool can scan those directly. You should be aware that detection depends on how resources were originally deployed—if the original manifest is not stored anywhere accessible to the tool, deprecations in that resource may not be detected. The tool supports Linux, macOS, and Windows across multiple CPU architectures, and can be installed via package managers or direct download.

The project maintains active engagement with community contributions and accepts pull requests. The codebase is written in Go and the tool is distributed as a compiled binary for multiple platforms, making deployment straightforward without requiring a runtime environment.