# Install kubent with Homebrew, Nix, scoop

Easily check your clusters for use of deprecated APIs. Version 0.7.3 via Homebrew; verified 2026-07-27. Also installable with nix: nix profile install nixpkgs#kubent.

## Install

```sh
sudo av install brew:kubent
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install kubent
```

  Evidence: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#kubent
```

  Evidence: nixpkgs package indexes: pkgs/by-name/ku/kubent/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

### Windows

- Scoop (92%):

```sh
scoop install main/kubent
```

  Evidence: Scoop official bucket manifest trees: bucket/kubent.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:kubent
- **Package manager:** Homebrew
- **Version:** 0.7.3
- **Source summary:** Easily check your clusters for use of deprecated APIs
- **Homepage:** <https://github.com/doitintl/kube-no-trouble>
- **Repository:** <https://github.com/doitintl/kube-no-trouble>
- **Last updated:** 2026-07-27T21:58:46+02:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- kubent (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 0.7.3
## Project history and usage

kubent is the Homebrew-packaged command name for Kube No Trouble, a Go CLI created to find Kubernetes objects that still use API versions scheduled for removal. It sits in the upgrade-preparation niche: operators run it before a cluster version jump so they can fix manifests, Helm releases, or last-applied kubectl state before the Kubernetes API server stops serving old versions.

### Project history

The project appeared publicly as Kube No Trouble in April 2020 with release 0.1.0. Its README ties the original motivation to the Kubernetes 1.16 wave of API deprecations, and its early releases quickly added static-file scanning and collector fixes so it could work outside a live cluster as well as against kubectl and Helm-maintained resources.

### Adoption history

kubent became a familiar checklist tool for Kubernetes platform teams because deprecated APIs are easy to miss in stored manifests and Helm release data. Homebrew, Scoop, Nix, and container-image distribution made it convenient to drop into upgrade runbooks and CI jobs without building from source.

### How it is used

Typical use points kubent at the active kubeconfig or an explicit kubeconfig path, then asks it to collect live resources, Helm manifests, or local YAML/JSON files and report API versions that match its deprecation rules. The project also documents JSON and CI-friendly output modes for automated gates.

### Why package nerds care

For package-maintainer culture, kubent is a compact example of the Kubernetes ecosystem producing tiny CLIs around version-skew pain. It matters less as a framework than as a practical binary that turns upstream API-removal policy into a package-manager-installable preflight check.

### Timeline

- 2020-04-09: Kube No Trouble 0.1.0 was published as the initial public release of kubent.
- 2020-08-11: Release 0.3.0 added support for reading manifests from local files and stdin.
- 2024-08-30: Release 0.7.3 was listed by the repository as a later tagged release.

### Related projects

- kubent is closely tied to kubectl, Helm, kubeconfig files, Open Policy Agent rules, and the Kubernetes deprecated API migration guidance.

### Sources

- <https://github.com/doitintl/kube-no-trouble>
- <https://github.com/doitintl/kube-no-trouble/releases/tag/0.1.0>
- <https://github.com/doitintl/kube-no-trouble/releases/tag/0.3.0>
- <https://kubernetes.io/docs/reference/using-api/deprecation-guide/>


## Security Notes

infrastructure mutation or orchestration signal.

- **Geiger risk:** orange / medium
- infrastructure mutation or orchestration signal


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: ~/.kube/config
## Other Package-Manager Records

- Nix - kubent: normalized package name match | nixpkgs package indexes: pkgs/by-name/ku/kubent/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- Scoop - main/kubent: normalized package name match | Scoop official bucket manifest trees: bucket/kubent.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/kubent.yml](https://github.com/mxcl/pkgdb/blob/main/combined/kubent.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph