// the find
kptdev/kpt
Automate Kubernetes Configuration Editing
kpt is a CLI tool for managing Kubernetes configuration as versioned, composable packages. It sits between raw kubectl and full GitOps operators — you pull a package, run KRM functions to transform YAML in place, then apply or push to Git. Aimed at platform teams managing many clusters or tenants who find Helm too opaque and kustomize too manual.
The 'configuration as data' model is coherent: transformations are pure functions over YAML ResourceLists, which means they're testable, composable, and language-agnostic. The inventory tracking (ResourceGroup CRD) gives you pruning and drift detection without requiring Flux or ArgoCD. The function catalog ships idempotent, off-the-shelf transformers (set-namespace, apply-setters, etc.) that cover 80% of real customization needs. CNCF Sandbox status means it has governance and isn't going to vanish when a Google team loses interest.
The learning curve is steep because kpt has its own mental model that doesn't map cleanly onto Helm or kustomize — adopters coming from either will spend real time unlearning. The KRM function pipeline runs containers by default, which makes local iteration slow and adds Docker-as-a-dependency friction in CI. Star count (1.8k) suggests limited community adoption compared to kustomize or Helm, meaning fewer StackOverflow answers and community packages. The alpha surface area is large — wasm functions, sync commands, live plan — and it's unclear which of these will stabilize vs. quietly disappear.