<p>i would want to know how do you manage your service with Helm ? </p>

<p>I already know that we are going to have more than <strong>200 microservices</strong>. <em>How to manage them easily</em> ? </p>

<p>Each microservice with is own yaml files (<strong>deployment,service,ingress ,values</strong> etc..)
 or <strong>one several large</strong> (deployment,ingress, etc.. )yaml files <strong>for all</strong> microservices and i push the values yaml file with the specific params for the application.</p>

morla
<p>I'd suggest aiming for an umbrella chart that includes lots of subcharts for the individual services. You can deploy each chart individually but using a single umbrella makes it easier to deploy the whole setup consistently to different environments.</p>

<p>Perhaps some microservices will be similar enough that for them you could use the same chart with different parameters (maybe including docker image parameter) but you'll have to work through them to see whether you can do that. You can include the same chart as a dependency multiple times within an umbrella chart to represent different services. </p>

<p>Ideally you also want a chart for a service to be individually-deployable so you can deploy and check that service in isolation. To do this you would give each chart its own resources including its own Ingress. But you might decide that for the umbrella chart you prefer to disable the Ingresses in the subcharts and put in a single fan-out Ingress for everything - that comes down to what works best for you. </p>
