kpt is a package-centric toolchain that enables a WYSIWYG configuration authoring, automation, and delivery experience, which simplifies managing Kubernetes platforms and KRM-driven infrastructure (e.g., Config Connector, Crossplane) at scale by manipulating declarative Configuration as Data.
Configuration as Data is an approach to management of configuration which:
- makes configuration data the source of truth, stored separately from the live state
- uses a uniform, serializable data model to represent configuration
- separates code that acts on the configuration from the data and from packages / bundles of the data
- abstracts configuration file structure and storage from operations that act upon the configuration data; clients manipulating configuration data don’t need to directly interact with storage (git, container images).
See the FAQ for more details about how kpt is different from alternatives.
You can ask anything about kpt in our public Dosu space.
Documentaion of the kpt project is in https://kpt.dev/.
Governance of the kpt project is described in the Governance repository.
Issues of all repos are managed under the issues of the kpt repo.
You can reach us in the #kpt channel on the Kubernetes Slack.
Discussion about all the repos in this organisation are in the Discussions of the kpt repo.
We have a kpt users mailing list what we do not use, we would like to encourage everyone to participate in the Discussions instead.
- kpt: The main logic of kpt.
- krm-functions-catalog: A set of curated functions to validate or mutate KRMs.
- krm-functions-sdk: An opinionated SDK to develop KRM functions.
- governance: Governance of the kpt project.
- .github: GitHub organisation level settings (this repo)