Is new K8s namespace per each feature branch deployment a good practice?

Question

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

Now we have multiple development namespaces (per team).

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

1-5 pods per feature-branch deployment.

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

The new idea is making a namespace per feature-branch deployment.

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.

Are there any advantages or disadvantages to this approach?

Answer 1

Its definitely a good approach to use namespaces for restricting the deployments to feature teams.
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.

1-5 pods per feature-branch deployment.

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.

Hope you are using rbac in k8s