Kubernetes namespaces partition workloads into virtual clusters so multiple teams or applications can safely share a physical cluster. Today, there is no common consensus on how to use Kubernetes namespaces and namespaced objects in relation to identity, resource limits, and security. As the number of teams, clusters, and namespaces grows within an organization, it becomes increasingly difficult to maintain any kind of coherence.
Amy Chen discusses how, by aligning identity, resource limits, and your application’s security posture, cluster operators can get more organizational mileage out of Kubernetes namespaces. She walks you through common scenarios of how organizations use namespaces today; breaks down namespaces in relation to your workloads and users; compares various approaches to namespace management; shows how to enforce RBAC, resource limits, and your application’s security posture within namespaces; and outlines friction in existing namespace management workflows.
©2019, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org