title: Put every configs in a single repo or each repo shoud have their own configs
body: <p>I'm trying to deploy a single project which is separated in multiple git repos, question bothering me is that: should we create a separate repo for kuberentes configs and deployment files or each repo should contain their own deployment code</p>
  
  <p>first solution puts everything in one place, which makes changes easier and also someone can monitor how our deployments changes, (also I think it might be easier to deploy whole project on different staging servers - we don't need to update every repo to change things like tokens, urls, db passwords, ...)</p>
  
  <p>but seconds solution lets devlopers on each repo easily change how their code is being deployed (each repo knows how to be deployed), also it might be easier to deploy the code (if we use a repo for kubernetes, code repo should somehow notify kubernetes repo that the code has been updated or a new docker image is ready on registry)</p>