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.
If you're just migrating I'd also recommend using helm.
When using helm create the chart definition within the source code repository of the application, https://helm.sh/docs/helm/helm_create/.
With an increasing number of services it can become harder and harder to manage so people have started to embrace a &quot;monorepo&quot; that contains a definition of the all the helm charts they currently have deployed and their respective versions. This way you can easily track when a version of service A was bumped and when a version of service B was bumped. https://www.infracloud.io/blogs/monorepo-ci-cd-helm-kubernetes/