Skip to main content

One Repository for Kubernetes configuration or one configuration per application repository

We are currently migrating our Services to a Kubernetes environment.

My question is if the configuration yaml file for each application

  • should be in the repository where the application source itself is stored,
  • or if there should be a centralized repository just for all the configuration files.

Currently I'm drifting more towards a centralized repository holding all configs, as dependencies on different versions of applications / services can be managed there. Another thing is that a change in the configuration should not trigger a rebuild of the application itself and this is also easier if the configuration and the application repositories are not the same.

wertzui
  • 101
  • 2