<p>I'm new in Kubernetes:</p>
<p>I have a multiple independent servers, they are based on spring boot java.
Each server has a separate independent database, where  database connection details are written in application.yml.</p>
<p>And I was wondering if i deploy in Kubernetes,
should I have a let say 15 different deployments , basically for each application.yml?</p>
<p>Could you please suggest the general flow or picture?</p>

gippo
<p>Flexibility comes when there is less or no dependency, so yes each service should be deployed and managed with its own deployment. So deployments just manage pod, and the pod is the smallest unit of the Kubernetes application, for example, let's say we have two services login and user service. Both have different container image so we need two different pods which mean two different deployments.</p>
<p>It will help to scale, rollout, clean and update independently. Plus in future, if you place monitoring etc it help you to identify object from the deployment which having issue.</p>
<p><a href="https://kubernetes.io/docs/concepts/workloads/controllers/deployment/" rel="nofollow noreferrer">kubernetes-deployment</a></p>
<p>Services like <a href="https://argo-cd.readthedocs.io/en/stable/" rel="nofollow noreferrer">ArgoCD</a> which work based on <a href="https://www.gitops.tech/" rel="nofollow noreferrer">GitOps</a> approach, sync applications from the git repository so in that case, it is also easier to sync applications independently.</p>
<p>In addition to that, Better to use a <a href="https://helm.sh/docs/intro/using_helm/" rel="nofollow noreferrer">helm</a> each service will represent a helm chart.</p>
