kit Components and Workflow Overview

4th chunk of `content/en/blog/_posts/2016-09-00-Deploying-To-Multiple-Kubernetes-With-Kit.md`

6ebb0fc7295d72e71e4b5883a73c074055a83c4eabee40230000000100000351

![](https://4.bp.blogspot.com/-BdD0AgQKFWY/V87u5p7uw2I/AAAAAAAAArM/Z6_279MSn2AVDmO192GtPPTuVBbLgsHCQCLcB/s640/kit.png)](https://4.bp.blogspot.com/-BdD0AgQKFWY/V87u5p7uw2I/AAAAAAAAArM/Z6_279MSn2AVDmO192GtPPTuVBbLgsHCQCLcB/s1600/kit.png)  
kit is comprised of several components each building on the next. The general flow is a developer commits code to their repository, an image is built and then kit-image-deployer commits the new image and tag to your manifests repository. From there the kit-deploymentizer runs, parsing all your manifest templates to generate the raw Kubernetes manifest files. Finally the kit-deployer runs and takes all the built manifest files and deploys them to all the appropriate clusters. Here is a summary of the components and the flow:  

**[kit-image-deployer](https://github.com/InVisionApp/kit-image-deployer)**

Title: kit Components and Workflow Overview

Summary

kit's architecture involves several components working in sequence: a developer commits code, an image is built, kit-image-deployer updates the manifest repository with the new image and tag, kit-deploymentizer generates Kubernetes manifest files from templates, and kit-deployer deploys these manifests to the designated clusters.