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 (VMware) 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.
- Title: Sharing is caring: Your Kubernetes cluster, namespaces, and you
- Release date: December 2019
- Publisher(s): O'Reilly Media, Inc.
- ISBN: 0636920363095
You might also like
Microservices Patterns Video Edition
"A comprehensive overview of the challenges teams face when moving to microservices, with industry-tested solutions to …
Kubernetes APIs under the hood
Kubernetes provides a powerful set of APIs and abstractions for building distributed systems. Additionally, it provides …
Building Microservices, 2nd Edition
Distributed systems have become more fine-grained as organizations shift from code-heavy monolithic applications to smaller, self-contained …
Amazon Web Services AWS LiveLessons 2nd Edition
More Than 17 Hours of Video Instruction More than 17 hours of video instruction on Amazon …