KubeLinter
docs.kubelinter.io
What it is
KubeLinter analyzes Kubernetes YAML, Helm charts, and Kustomize manifests for configuration practices related to security and production readiness. Its default checks flag issues such as containers running as root, insufficiently limited privileges, and sensitive data stored outside secrets. Teams can turn checks on or off and define custom checks to reflect their own policies, using YAML configuration and CEL expressions. It can lint individual Kubernetes YAML files or Helm and Kustomize directories. Failed checks include remediation recommendations and produce a non-zero exit code, which can make them useful in automated workflows. Results can be written as plain text, JSON, or SARIF, including more than one format in a run. The project documents integrations with pre-commit hooks and GitHub Actions, plus installation through Go, release binaries, package managers, nix-shell, or Docker. It runs on Linux, macOS, or in a self-hosted setup. KubeLinter is free under Apache License 2.0; its documentation notes that commands, flags, and configuration formats may change.
Spec sheet
- What it does
- KubeLinter statically analyzes Kubernetes YAML, Helm charts, and Kustomize manifests for best practices, production readiness, and security.Read 5 Oct 2026 · github.com
- Integrations
- The project documents use with pre-commit hooks, a Docker-based pre-commit hook, and a GitHub Action for CI.Read 5 Oct 2026 · github.com
- License
- KubeLinter is licensed under the Apache License 2.0.Read 5 Oct 2026 · github.com
- Maker
- The repository says KubeLinter was created by StackRox and is now powered by Red Hat.Read 5 Oct 2026 · github.com
- Custom policies
- Users can enable or disable checks and create custom checks to match organizational policies.Read 5 Oct 2026 · github.com
- Default checks
- Its default checks cover issues such as running containers as non-root, enforcing least privilege, and storing sensitive information only in secrets.Read 5 Oct 2026 · github.com
- Findings
- When a lint check fails, KubeLinter reports remediation recommendations and returns a non-zero exit code.Read 5 Oct 2026 · github.com
- Image verification
- KubeLinter container images are signed with cosign, and the project provides a public key for verification.Read 5 Oct 2026 · github.com
- Input types
- KubeLinter can lint Kubernetes YAML files, Helm chart directories, and Kustomize directories.Read 5 Oct 2026 · github.com
- Installation
- The project documents installation using Go, release binaries, Homebrew or LinuxBrew, nix-shell, and Docker.Read 5 Oct 2026 · github.com
- Notable limitation
- The project notes that command usage, flags, and configuration file formats may change in the future.Read 5 Oct 2026 · github.com
- Report formats
- It supports plain text, JSON, and SARIF output, including writing multiple formats in one run.Read 5 Oct 2026 · github.com
- Security reporting
- The security policy directs people reporting vulnerabilities to Red Hat's Product Security team for confidential disclosure.Read 5 Oct 2026 · github.com
- Support and community
- The project points users to its Slack workspace to engage with maintainers and other users.Read 5 Oct 2026 · github.com
Plans and prices
Strong points and limits
Strong points
- Checks Kubernetes YAML, Helm, and Kustomize inputs
- Custom checks support organizational policies
- Failed checks include remediation recommendations
- Can emit multiple report formats in one run
- Free under Apache License 2.0
Limits
- Commands, flags, and configuration formats may change
Who it suits
KubeLinter suits teams that maintain Kubernetes, Helm, or Kustomize configurations and want configurable checks in local or CI workflows. It also fits organizations that need findings in plain text, JSON, or SARIF.
Verdict
KubeLinter combines configurable Kubernetes configuration checks with report formats and CI integrations. Its stated potential for changes to commands, flags, and configuration formats is worth accounting for when building workflows around it.
Where Specifiction places it
- Infrastructure Policy as Code Tools#14 of 257.6