<p>I'm trying to figure out how to organize K8s namespaces for the development cluster.</p>

<p>Now we have multiple development namespaces (per team).</p>

<p>There are tons of pods (about 100-200) in a single namespace.</p>

<p>1-5 pods per feature-branch deployment.</p>

<p>We use Helm to make deployments. But some of the teammates say that it's hard to manage it.</p>

<p>The new idea is making a namespace per feature-branch deployment.</p>

<p>Now, I see the main issue is in TLS (and others) secrets sync sharing across namespaces. But it can be resolved by making a CronJob.</p>

<p>Are there any advantages or disadvantages to this approach?</p>

visortelle
<p>Its definitely a good approach to use namespaces for restricting the deployments to feature teams.<br/>
But deploying 50+ pods becomes difficult to manage per namespace, especially if the pods contains 10+ conatiners. So you will tend to manage 50X10=500 containers per deployment team.<br/></p>

<blockquote>
  <p>1-5 pods per feature-branch deployment.</p>
</blockquote>

<p>This is really a great way to go about using a namespace, but still yet you will have lots and lots of namespace to remember when you initally said you have arounf 100-200 pods.</p>

<p><strong>Hope you are using rbac in k8s</strong></p>
