Is it anti-pattern to have multiple environments under a single namespace?

• namespace-configuration-operator

  4 218 6.1 Go

  The namespace-configuration-operator helps keeping configurations related to Users, Groups and Namespaces aligned with one of more policies specified as a CRs

  

  If you go multiple-tenant, use at least OKD and not blank Kubernetes. Additionally https://github.com/redhat-cop/namespace-configuration-operator to improve on boarding and allow teams to create namespaces/projects freely

• CodeRabbit

  coderabbit.ai featured

  CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

  

• hierarchical-namespaces

  8 630 3.7 Go

  Home of the Hierarchical Namespace Controller (HNC). Adds hierarchical policies and delegated creation to Kubernetes namespaces for improved in-cluster multitenancy.

  

  I would say it’s an anti-pattern since using a namespace for multiple environments will be a pain. Not sure what you mean by CRDs though. There is an addon that gives you namespace hierarchies. I.e. each team gets a namespace and they can have sub-namespaces for environments. Check it out: https://github.com/kubernetes-sigs/hierarchical-namespaces

• capsule

  5 1,633 9.3 Go

  Multi-tenancy and policy-based framework for Kubernetes.

  

Suggest a related project