This message was deleted.

Hey! I'm working on a demo including multiple teams, environments and services - curious how teams usually set-up Kubernetes namespaces? Please comment to provide details on your typical set-up 🙏

If you get the matrix of every service and every tenant, that's how we divide up our namespaces.

@Troy Knapp by tenant, do you mean dev, stage, prod? or something else?

I mean by tenant. We have a cluster per environment like dev, stage, and prod. We have services in each so our namespaces are like <service>-<tenant>.

aah understood, thanks for the clarification! 🙌

We got a cluster per environment and certain nodes reserved just for ops tools

Am I the only one with the 4th option 🙂

@Abhibhaw Asthana you're not! I posted the same survey on LinkedIn and somebody else selected that option as well. I am sure they are more 🙂

We (https://www.cecg.io/) build this solution for customers all the time. The most common implementation choice atm is using HNC. Every department gets a parent namespace, every team gets a child namespace under that, then every serivce gets its own namespace under that Dept -> Team -> App In the dev cluster, we then recommend that each app creates multiple lightweight envs under their App namespace for different types of testing e.g. app-nft app-functional app-integreated

Kind of a weird setup for us as we have single tenant applications so we have clusters for <environment>-<region> and namespaces per customer. Slowly migrating to multi tenant solutions where it's a namespace per "cell" of multitenant services