kubernetes-sigs/kustomize

Customization of kubernetes YAML configurations

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 54 minutes ago
Added to GitGenius on September 5th, 2026
Created on May 11th, 2018
Open Issues & Pull Requests: 187 (+0)
GitHub issues: Enabled
Number of forks: 2,417
Total Stargazers: 12,156 (+1)
Total Subscribers: 108 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Kustomize is a template-free customization tool for Kubernetes YAML configurations that lets you patch and modify raw resource files while keeping originals untouched and reusable.

The tool solves the problem of managing multiple variants of Kubernetes configurations without templating languages or duplication. It works by declaring customizations in a kustomization file alongside your YAML resources, then applying patches, labels, and other modifications at build time. The approach is declarative like make and operates on text like sed, but with semantic understanding of Kubernetes API objects.

Kustomize suits teams managing multiple deployment environments from a shared base configuration. It works well when your original YAML comes from an upstream source you want to track separately, since overlays let you layer environment-specific changes on top without modifying the base. The tool integrates directly into kubectl, so it's available without separate installation for recent Kubernetes versions. Choose it if you prefer composition and patching over templating, and if your workflow benefits from keeping base configurations and environment variants in separate directories that can live in different repositories.

The project maintains active engagement with its community through documentation and examples. Development follows a structured approach with regular updates synchronized to Kubernetes releases. The tool receives ongoing maintenance to keep pace with Kubernetes API evolution and user needs.