A lightweight tool to facilitate config reuse, designed for GitOps, config as data, and composition with other tools and formats.https://twitter.com/GoogleOSS/status/1245026820979859464 …
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
The other main capability needed to enable reuse is the ability to customize configuration files for specific use cases. That’s where the most diverse preferences are evident. kpt supports generation, transformation, and validation functions written in any programming language.
kpt accomplishes this by representing configuration as data, specifically Kubernetes resources serialized as YAML or JSON. The configuration-as-data approach builds upon the design of the Kubernetes resource model (KRM): https://github.com/kubernetes/community/blob/master/contributors/design-proposals/architecture/resource-management.md …
It builds directly upon prior work in Kubernetes, such as https://github.com/kubernetes/community/blob/master/contributors/design-proposals/architecture/declarative-application-management.md …, bulk operations in kubectl (https://github.com/kubernetes/kubernetes/pull/1007/files …), apply (http://issues.k8s.io/1702 ), andhttps://github.com/kubernetes-sigs/kustomize …
Though it’s in its early stages, I hope that kpt will not only fill a gap in the existing tool landscape, but will also inspire more tools designed to interoperate with other configuration and deployment tools and workflows in the Kubernetes ecosystem.
I don't speak emoji :-). One of the pieces of magic compared to git subtree is that kpt can project a subdirectory of a repo (such as a package library repo) into another repo. Seems minor, but makes package management much easier and more flexible.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.