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 …
Show this thread
-
git is the most common source of truth for declarative configuration files, and users are increasingly driving deployment workflows from changes in git, either with traditional CI/CD tools or dedicated GitOps tools. kpt facilitates declarative workflows directly around git.
Show this thread
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 …
Show this thread -
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 …
Show this thread -
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.
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.