kpt v1.0.0 is released: After many years and much development, the kpt

The kpt community released v1.0.0 on November 5, 2026, after several years in pre-release. CNCF Blog (Eng)'s report, by epower, says the last twelve months stabilised the APIs, deprecated unused features, and integrated Porch (Package ORCHestration) back into the kpt organization. The community calls every component stable and kpt ready for widespread adoption.

This piece is for teams managing configuration for Kubernetes applications, clusters, or any resources through Kubernetes APIs. It covers standalone kpt and Porch in v1.0.0, the builder changes, how to get involved, the deprecated-feature and KRM limits, and the weekly forum after the release.

01What Kpt v1.0.0 is released shipped

Standalone kpt provides lightweight configuration package management for applications running on Kubernetes, based on config as data principles. Those principles allow declarative manipulation and verification of configuration for cloud native applications, clusters, or any resources managed through Kubernetes APIs. Everything in kpt is expressed using KRM. The framework describes manipulation and validation steps in a package, then autonomously converts generic KRM into a deployable model for a specific site or application. That is reproducible manipulation without the limitations of templating.

Porch (Package ORCHestration) orchestrates kpt packages at scale in a zero-touch GitOps workflow. Over the last twelve months the community integrated Porch back into the kpt organization so it shares governance with the rest of the toolchain. The November 5, 2026 post calls v1.0.0 a big step after several years in pre-release. It says all components are stable, and that the community is actively building a simple, comprehensive, lightweight, and modular framework for the lifecycle management of any Kubernetes resources.

02What changed for builders in Kpt v1.0.0 is released

Builders inherit three changes from the twelve months before November 5, 2026. The kpt community stabilised the APIs, deprecated unused features, and integrated Porch back into the kpt organization. Release status moves from several years of pre-release to v1.0.0. Governance becomes one complete toolchain under common governance, a comprehensive system for GitOps-based package management that is modular enough to add value to any workflow. Widespread adoption is the claim attached to v1.0.0, on the grounds that every component is stable.

A builder still writes packages as KRM and records manipulation and validation steps for kpt to apply. kpt converts that generic KRM into a deployable model for one site or one application, and the project says the output is reproducible. Declarative verification covers cloud native applications, clusters, and resources managed through Kubernetes APIs. Porch orchestrates those packages in a zero-touch GitOps workflow. Package ORCHestration now sits inside the kpt organization, so packaging and orchestration are one toolchain under common governance.

03How to install or upgrade Kpt v1.0.0 is released

The kpt project meets weekly, on Wednesdays at 2pm CET. It uses GitHub to collaborate on issues and discussions, and the kpt channel on the Kubernetes slack for ad hoc communication. People already using kpt who want a new feature, or who want to help improve it, are asked to reach out. epower writes that the community would be delighted to see them. Anyone who finds the toolchain interesting and would like to know more is asked to reach out.

04Gotchas and compatibility in Kpt v1.0.0 is released

Compatibility in v1.0.0 rests on work done while the APIs were stabilised. Unused features were deprecated across the last twelve months. The November 5, 2026 post states the deprecation and does not name each unused feature. Everything in kpt is expressed using KRM. Manipulation and validation steps sit on the package, and kpt autonomously converts generic KRM into a deployable model for a specific site or application. The post describes that path as reproducible manipulation without the limitations of templating.

Integrating Porch back into the kpt organization puts package management and orchestration under common governance, which the post calls the complete toolchain. Porch orchestrates kpt packages at scale in a zero-touch GitOps workflow. Standalone kpt remains the package layer for applications on Kubernetes, for clusters, and for any resources managed through Kubernetes APIs. Config as data stays the rule for declarative manipulation and verification. Improvement requests go to GitHub issues and discussions and to the Kubernetes slack channel named kpt.

05What to watch after Kpt v1.0.0 is released

The kpt community is actively building a simple, comprehensive, lightweight, and modular framework for the lifecycle management of any Kubernetes resources. The post says the components are stable for widespread adoption after several years in pre-release. Twelve months before v1.0.0 covered API stabilisation, deprecation of unused features, and Porch's return to the kpt organization. Meetings of the project are weekly, Wednesdays at 2pm CET. GitHub holds issues and discussions. The kpt channel on the Kubernetes slack handles ad hoc communication.

People already using kpt who want a new feature, or who want to help improve the toolchain, are invited to reach out. epower says the kpt community would be delighted to see them. People who want to know more are invited on the same terms. The November 5, 2026 release presents v1.0.0 as ready for widespread adoption, with standalone kpt for config-as-data packages and Porch for zero-touch GitOps orchestration at scale, both now under common governance in the kpt organization.