kit's Workflow, Suitability, and Components

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

96d50dfd2510160e6b5f05a83db1accd3c0f0e21a81a566d000000010000063c

Developers simply commit code to their branches as normal and kit deploys to all clusters running that service. Kit then manages updating the image and tag that is used for a given service directly to the repository containing all your kit manifest templates. This means any and all changes to your clusters, from environment variables, or configurations to image updates are all tracked under source control history providing you with an audit trail for every cluster you have.  

We made all of this Open Source so you can [check out the kit repo](https://github.com/InVisionApp/kit)!  

**Is kit Right For Us?**  

If you are running Kubernetes across several clusters (or namespaces) all needing to continuously deploy, you bet! Because using kit doesn’t require hosting any external server, your team can leverage the webhooks you probably already have with github and your CI/CD system to get started. From there you create a repo to host your Kubernetes manifest files which tells what services are deployed to which clusters. Complexity of these files is greatly simplified thanks to kit’s templating engine.The kit-image-deployer component is incorporated into the CI/CD process and whenever a developer commits code to master and the build passes, it’s automatically deployed to all configured clusters.  

**So What Are The Components?**  
[![](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)

Title: kit's Workflow, Suitability, and Components

Summary

kit automates deployments to all clusters when developers commit code, updating image and tag information in the manifest repository. All changes, including environment variables and configurations, are tracked in source control for auditing. It is open source and ideal for Kubernetes environments needing continuous deployments across multiple clusters, leveraging existing webhooks and CI/CD systems without hosting an external server.