title: Different deployment configurations using Helm
body: <p>I would like to have a slightly different deployment configuration in different invironments. That is, in Prod and Ver, I don't want all containers to be deployed.</p>
  
  <p>With docker-compose we solve that by having incremental docker-compose files that we combine, like: <code>docker-compose up -f docker-compose.yml -f docker-compose-prod.yml</code></p>
  
  <p>How can that be done using Helm charts?
  We have a structure with Chart.yaml and values.yaml in the top, and then one yaml file per container in a subfolder. The naive solution would be to copy that structure and leave out some of the chart files, but I would prefer to have only one file (at most one file!) per service.</p>
  
  <p>We deploy to AKS using CircleCI.</p>
  
  <p>To summarize: 
  Today, each service has it's own yaml file, and on every deploy, all of them gets deployed. I want to configure my charts so that only a subset of the services gets deployed in certain environments.</p>
  
  <p>EDIT:</p>
  
  <p>kubectl has the the possibility to use selectors, like <code>kubectl create cfg.yaml --selector=tier=frontend</code> or <code>kubectl create cfg.yaml --selector=environment=prod</code> and I already tag my containers, so that would have been simple. But <code>helm install</code> does not have the possibility to accept a similar flag and pass it to kubectl.</p>