Our great sponsors
-
namespace-configuration-operator
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
-
hierarchical-namespaces
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
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Related posts
- LoadBalancer type service on bare-metal
- 5-Step Approach: ProjectSveltos Event Framework for Kubernetes Deployment with Cilium Gateway API
- 5-Step Approach: Projectsveltos for Kubernetes add-on deployment and management on RKE2
- Amazon EC2 Enhances Defense in Depth with Default IMDSv2
- EKS secrets - Bitnami sealed secrets or KMS?